- Pharo-users - lists.pharo.org

VM/Image magic numbers (Re: Pharo 6 snap install)

by Ben Coman

The "magic decode for image files" seems related and possibly *very* useful.... http://forum.world.st/magic-decode-for-image-files-td4941712.html#a4941837 Now traditionally the VM has been backward compatible with old Images, but Pharo doesn't necessarily adhere to that and policy IIUC is release specific VM/Image pairs. So does Pharo require extra magic numbers to co-ordinate this? And how would this interact with OpenSmalltalk policy on these magic numbers? cheers -ben On Sat, Apr 15, 2017 at 4:20 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > This is what we always have when we release and we freeze it. > The vm 60 will be compatible with latest pharo 60 image. > > > > On Fri, Apr 14, 2017 at 12:09 PM, Luke Gorrie <luke(a)snabb.co> wrote: >> >> On 14 April 2017 at 08:53, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>> >>> We always try to have a major release around mid/end of april >> >> >> Once the dust settles, I think it would be wonderful to have this invariant: >> >> - The latest Pharo VM source release is compatible with the latest Pharo image. >> >> This would make it easy for me to help nix users. My job will be to package the latest source release of the VM, period, and I will know that users can use this to run the latest image. I don't have much scope to screw things up and make people sad e.g. by shipping a bad commit from the master branch. >> >> (Of course it makes life harder for you upstream Pharo maintainers. Now updating the VM source release is a blocker for releasing a new image. Could be that this is too constraining in practice, I dunno. I'm just a guy who wants to setup a stable Pharo that I can use to build an application :-)) >> >> >

April 14, 2017

Re: [Pharo-users] Pharo6 server deployment and no home directory

by Juraj Kubelka

Hi, > El 14-04-2017, a las 16:17, Holger Freyther <holger(a)freyther.de> escribiÃ³: > > Hi, > > as Pharo6 is around the corner I have moved my CI build from tracking Pharo5 to Pharo6 but I run into a problem. Either if $HOME is not set at all or $HOME points to a wrong directory I run into the error below. > > As this is a server application and I run multiple VMs with the same image and there is no home directory I would prefer that no information is persisted at all. Can this be done? Have there been any changes in Pharo6 in regard to this? Do you think that checking if `FileIdentifier home` exist solves the issue? Can we detect headless state? > > It also seems to change from Fuel->Ston for the identifier? Is this intended? Yes, this is intended and should not produce problems. Juraj > > holger > > > > HOME=/home/blabla ./vm/pharo --nodisplay My.image eval --save '(NonInteractiveTranscript onFileNamed: #stdout)' install > PrimitiveFailed: primitive #createDirectory: in UnixStore failed > UnixStore(Object)>>primitiveFailed: > UnixStore(Object)>>primitiveFailed > UnixStore(DiskStore)>>createDirectory: > UnixStore(FileSystemStore)>>ensureCreateDirectory: > UnixStore(FileSystemStore)>>ensureCreateDirectory: > UnixStore(FileSystemStore)>>ensureCreateDirectory: > FileSystem>>ensureCreateDirectory: > FileReference>>ensureCreateDirectory > FileLocator(AbstractFileReference)>>ensureCreateDirectory > GlobalIdentifierFuelPersistence(GlobalIdentifierPersistence)>>ensureDirectory > GlobalIdentifierFuelPersistence(GlobalIdentifierPersistence)>>save: > GlobalIdentifierFuelPersistence(GlobalIdentifierPersistence)>>load: > GlobalIdentifierFuelPersistence(GlobalIdentifierPersistence)>>ensure: > GlobalIdentifierStonPersistence(GlobalIdentifierPersistence)>>ensure: > GlobalIdentifier>>ensure > GlobalIdentifier class>>initializeUniqueInstance > GlobalIdentifier class>>uniqueInstance > SystemSettingsPersistence class>>resumeSystemSettings > [ :persistence | persistence resumeSystemSettings ] in PharoCommandLineHandler>>runPreferences in Block: [ :persistence | persistence resumeSystemSettings ...etc... > BlockClosure>>cull: > SystemDictionary(Dictionary)>>at:ifPresent: > SmalltalkImage>>at:ifPresent: > PharoCommandLineHandler>>runPreferences > PharoCommandLineHandler>>activate > PharoCommandLineHandler class(CommandLineHandler class)>>activateWith: > [ super activateWith: aCommandLine ] in PharoCommandLineHandler class>>activateWith: in Block: [ super activateWith: aCommandLine ] > NonInteractiveUIManager(UIManager)>>defer: > PharoCommandLineHandler class>>activateWith: > [ aCommandLinehandler activateWith: commandLine ] in BasicCommandLineHandler>>activateSubCommand: in Block: [ aCommandLinehandler activateWith: commandLine ] > BlockClosure>>on:do: > >

April 14, 2017

Re: [Pharo-users] How can I set the SmaccDebugParser in Moose

by Andrei Chis

Not exactly sure how to do to it because I never used it. >From what I see in SmaCCParserDebugger>>handlesContext: if you have in the stack a context created by SmaCCParser>>parse you should have a 'SmaCCParser' button at the top right of the window. But maybe John can provide you with more details. Cheers, Andrei On Fri, Apr 14, 2017 at 2:45 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Andrei? > Help? > > > > On Fri, Apr 7, 2017 at 3:14 PM, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > >> Hi >> >> I found the SmaCCParserDebugger and I found the debug menu in the Smacc >> tool. >> Now I get a GT and byteCode debugger but I do not find a way to make the >> new debugger actif. >> >> Stef >> > >

April 14, 2017

Re: [Pharo-users] Pharo 6 snap install

by Stephane Ducasse

This is what we always have when we release and we freeze it. The vm 60 will be compatible with latest pharo 60 image. On Fri, Apr 14, 2017 at 12:09 PM, Luke Gorrie <luke(a)snabb.co> wrote: > On 14 April 2017 at 08:53, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > >> We always try to have a major release around mid/end of april >> > > Once the dust settles, I think it would be wonderful to have this > invariant: > > - The latest Pharo VM source release is compatible with the latest Pharo > image. > > This would make it easy for me to help nix users. My job will be to > package the latest source release of the VM, period, and I will know that > users can use this to run the latest image. I don't have much scope to > screw things up and make people sad e.g. by shipping a bad commit from the > master branch. > > (Of course it makes life harder for you upstream Pharo maintainers. Now > updating the VM source release is a blocker for releasing a new image. > Could be that this is too constraining in practice, I dunno. I'm just a guy > who wants to setup a stable Pharo that I can use to build an application > :-)) > > >

April 14, 2017

Pharo6 server deployment and no home directory

by Holger Freyther

Hi, as Pharo6 is around the corner I have moved my CI build from tracking Pharo5 to Pharo6 but I run into a problem. Either if $HOME is not set at all or $HOME points to a wrong directory I run into the error below. As this is a server application and I run multiple VMs with the same image and there is no home directory I would prefer that no information is persisted at all. Can this be done? Have there been any changes in Pharo6 in regard to this? It also seems to change from Fuel->Ston for the identifier? Is this intended? holger HOME=/home/blabla ./vm/pharo --nodisplay My.image eval --save '(NonInteractiveTranscript onFileNamed: #stdout)' install PrimitiveFailed: primitive #createDirectory: in UnixStore failed UnixStore(Object)>>primitiveFailed: UnixStore(Object)>>primitiveFailed UnixStore(DiskStore)>>createDirectory: UnixStore(FileSystemStore)>>ensureCreateDirectory: UnixStore(FileSystemStore)>>ensureCreateDirectory: UnixStore(FileSystemStore)>>ensureCreateDirectory: FileSystem>>ensureCreateDirectory: FileReference>>ensureCreateDirectory FileLocator(AbstractFileReference)>>ensureCreateDirectory GlobalIdentifierFuelPersistence(GlobalIdentifierPersistence)>>ensureDirectory GlobalIdentifierFuelPersistence(GlobalIdentifierPersistence)>>save: GlobalIdentifierFuelPersistence(GlobalIdentifierPersistence)>>load: GlobalIdentifierFuelPersistence(GlobalIdentifierPersistence)>>ensure: GlobalIdentifierStonPersistence(GlobalIdentifierPersistence)>>ensure: GlobalIdentifier>>ensure GlobalIdentifier class>>initializeUniqueInstance GlobalIdentifier class>>uniqueInstance SystemSettingsPersistence class>>resumeSystemSettings [ :persistence | persistence resumeSystemSettings ] in PharoCommandLineHandler>>runPreferences in Block: [ :persistence | persistence resumeSystemSettings ...etc... BlockClosure>>cull: SystemDictionary(Dictionary)>>at:ifPresent: SmalltalkImage>>at:ifPresent: PharoCommandLineHandler>>runPreferences PharoCommandLineHandler>>activate PharoCommandLineHandler class(CommandLineHandler class)>>activateWith: [ super activateWith: aCommandLine ] in PharoCommandLineHandler class>>activateWith: in Block: [ super activateWith: aCommandLine ] NonInteractiveUIManager(UIManager)>>defer: PharoCommandLineHandler class>>activateWith: [ aCommandLinehandler activateWith: commandLine ] in BasicCommandLineHandler>>activateSubCommand: in Block: [ aCommandLinehandler activateWith: commandLine ] BlockClosure>>on:do:

April 14, 2017

Re: [Pharo-users] Traits score: Squeak: 1, Pharo5: 0

by Hilaire

I tried but I can't reproduce the case with dummy code. I can share privately an image though. Hilaire Le 14/04/2017 Ã 15:24, Denis Kudriashov a Ã©crit : > > Could you create example set of packages to reproduce problem? (to be > not dependant on your private code) > -- Dr. Geo http://drgeo.eu

April 14, 2017

Re: [Pharo-users] Export MongoDB to sql format

by Ben Coman

On Fri, Apr 14, 2017 at 5:13 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > On 13 April 2017 at 22:23, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> >> On 13 Apr 2017, at 19:26, Asbath Sama biyalou via Pharo-users < >> pharo-users(a)lists.pharo.org> wrote: >> >> >> *From: *Asbath Sama biyalou <asamabiyalou(a)yahoo.com> >> *Subject: **Export MongoDB to sql format* >> *Date: *13 April 2017 at 19:26:25 GMT+2 >> *To: *Pharo users users <pharo-users(a)lists.pharo.org> >> >> >> Hello Everyone. >> >> I think this is not the right place for this question. But I am doing a >> work with Pharo. >> >> I use MongoDB with Voyage. But I am asked to export my database in sql >> format. >> >> I want to know if there is a way to export mongoDB in sql. >> >> >> there is not. >> a nosql database will have problems to export its data as sql. >> of course it can be done (as everything), but it is a manual task :S >> >> > This sort of questions most strangest ones , that i always wonder.. > Pure supposition... Because the corporate policy *only* allows relational database, but nosql was a better solution, but needs fake that its relational. cheers -ben > Like people who buying microwave asking: cool , now how i could fit a coal > burner to it? > > Why???? I mean if you need your traditional oven, they why even bother to > buy a microvawe in a first place? > > > cheers, >> Esteban >> >> >> Thanks. >> >> >> Asbath >> >> > > > -- > Best regards, > Igor Stasenko. >

April 14, 2017

Re: [Pharo-users] Traits score: Squeak: 1, Pharo5: 0

by Denis Kudriashov

Hi. Could you create example set of packages to reproduce problem? (to be not dependant on your private code) 2017-04-14 14:41 GMT+02:00 Hilaire <hilaire(a)drgeo.eu>: > Tested on Pharo6, result is the same :( > Traits logic is lost when saving the package. > > Squeak: 1 - Pharo6: 0 > > > Le 14/04/2017 Ã 14:33, Hilaire a Ã©crit : > > So it looks like Squeak[1] is capable to produce a correct .mcz file, > > out of a package coming with Traits and class. > > By correct, read the Traits logic is not lost. > > > > Hilaire > > > > [1] I tested with a Squeak6 alpha waiting somewhere on my disk > > > > -- > Dr. Geo > http://drgeo.eu > > >

April 14, 2017

Re: [Pharo-users] Traits score: Squeak: 1, Pharo5: 0

by Hilaire

Tested on Pharo6, result is the same :( Traits logic is lost when saving the package. Squeak: 1 - Pharo6: 0 Le 14/04/2017 Ã 14:33, Hilaire a Ã©crit : > So it looks like Squeak[1] is capable to produce a correct .mcz file, > out of a package coming with Traits and class. > By correct, read the Traits logic is not lost. > > Hilaire > > [1] I tested with a Squeak6 alpha waiting somewhere on my disk > -- Dr. Geo http://drgeo.eu

April 14, 2017

Re: [Pharo-users] Export MongoDB to sql format

by Dimitris Chloupis

Some traditional ovens cook some foods better the answer is always "because its a complex world and any effort to simplify it is doomed to fail" On Fri, Apr 14, 2017 at 12:14 PM Igor Stasenko <siguctua(a)gmail.com> wrote: > On 13 April 2017 at 22:23, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> >> On 13 Apr 2017, at 19:26, Asbath Sama biyalou via Pharo-users < >> pharo-users(a)lists.pharo.org> wrote: >> >> >> *From: *Asbath Sama biyalou <asamabiyalou(a)yahoo.com> >> *Subject: **Export MongoDB to sql format* >> *Date: *13 April 2017 at 19:26:25 GMT+2 >> *To: *Pharo users users <pharo-users(a)lists.pharo.org> >> >> >> Hello Everyone. >> >> I think this is not the right place for this question. But I am doing a >> work with Pharo. >> >> I use MongoDB with Voyage. But I am asked to export my database in sql >> format. >> >> I want to know if there is a way to export mongoDB in sql. >> >> >> there is not. >> a nosql database will have problems to export its data as sql. >> of course it can be done (as everything), but it is a manual task :S >> >> > This sort of questions most strangest ones , that i always wonder.. > Like people who buying microwave asking: cool , now how i could fit a coal > burner to it? > > Why???? I mean if you need your traditional oven, they why even bother to > buy a microvawe in a first place? > > > cheers, >> Esteban >> >> >> Thanks. >> >> >> Asbath >> >> > > > -- > Best regards, > Igor Stasenko. >

April 14, 2017