April 2017 - Pharo-users - lists.pharo.org

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

by Hilaire

Indeed that's it. Adding methods after the second traits was created shows up the bug. I open a ticket. https://pharo.fogbugz.com/f/cases/19938/Traits-methods-flattened Le 15/04/2017 Ã 08:14, Nicolai Hess a Ã©crit : > > How to reproduce: > -- Dr. Geo http://drgeo.eu

April 15, 2017

Pharo6 ombu-session files in pharo-local

by Holger Freyther

Hi, as part of moving a test image from Pharo5 to Pharo6 I also noticed that on each start a new "ombu-session" folder will be created (and never cleaned up). For a server-side deployment this is quite unfortunate as I want/need to use a fixed amount of disk space. I think Norbert has similar concerns with this feature. We are using "image-launch" to run the image and then either systemd|monit|runit|kubernetes will execute (and re-execute) image-launch. So potentially many many folders are created and never used. On deployments with many images, it is rare to make online changes and even more rare to try to recover them. Would it be possible to create the underlying storage or disable it completely? thank you holger

April 15, 2017

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

by Hilaire

Great! It is nice you can reproduce it, because my attempt failed with the exemple package attached. Le 15/04/2017 Ã 08:14, Nicolai Hess a Ã©crit : > > 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) > > > > > How to reproduce: > -- Dr. Geo http://drgeo.eu

April 15, 2017

Re: [Pharo-users] Pharo 6 snap install

by Alistair Grant

On Sat, Apr 15, 2017 at 09:50:29AM +0200, Luke Gorrie wrote: > On 15 April 2017 at 09:12, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > On Sat, Apr 15, 2017 at 06:43:39AM +0200, Luke Gorrie wrote: > > The latest stable image release is Pharo-50771.image. > > The latest stable VM source release is pharo-vm-2016.02.18. > > These two releases are not compatible: This interpreter (vers. 6505) > cannot > > read image file (vers. 6521). > > Is this from a VM you built yourself? > > > This is a VM built from source during packaging for NixOS Linux. > > > What's the output of: > > $ pharo --version > > > Here it is: > > > $ pharo-vm-nox --version > 3.9-7 #1 Tue Mar 28 16:26:45 UTC 2017 gcc 5.4.0 [Production ITHB VM] > NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: > 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Apr 5 2016 > NBCogit NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: > 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Apr 5 2016 > https://github.com/pharo-project/pharo-vm.git Commit: > ba1aa855f546b084ec0ebdeb85a36f2352f97b49 Date: 2016-02-18 17:17:13 +0100 > By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #15040 > Linux localhost 4.4.23 #1-NixOS SMP Fri Sep 30 08:20:43 UTC 2016 i686 GNU/ > Linux > plugin path: /nix/store/ > 5bm2pwrkd1083sb1f1rf0jz20cw87yya-pharo-vm-i386-2016.02.18/lib/ > pharo-vm-i386-2016.02.18/ [default: /nix/store/ > 5bm2pwrkd1083sb1f1rf0jz20cw87yya-pharo-vm-i386-2016.02.18/lib/ > pharo-vm-i386-2016.02.18/] > > > Note that the date 2016-02-18 corresponds with the latest non-spur source > tarball release at http://files.pharo.org/vm/src/vm-unix-sources/ > > > I just downloaded: > > $ curl http://get.pharo.org/50+vm | bash > > And it started without problem. > > > I *think* the difference is that you are downloading the VM as a binary and I > am downloading it as source code, and we get different versions because > pharo.org is regularly shipping updated binaries but not updating the source > code releases at the same time. So the source releases lag behind over time and > now it's at the point that they can't run the 5.0 image. How about trying: $ git clone https://github.com/pharo-project/pharo-vm.git $ cd pharo-vm $ git checkout b8ec25a570d7539653e1d793e97609adb509aaed and build that? It should be the source code for the binary VM on get.pharo.org. Cheers, Alistair

April 15, 2017

Re: [Pharo-users] Pharo 6 snap install

by Luke Gorrie

On 15 April 2017 at 09:12, Alistair Grant <akgrant0710(a)gmail.com> wrote: > On Sat, Apr 15, 2017 at 06:43:39AM +0200, Luke Gorrie wrote: > > The latest stable image release is Pharo-50771.image. > > The latest stable VM source release is pharo-vm-2016.02.18. > > These two releases are not compatible: This interpreter (vers. 6505) > cannot > > read image file (vers. 6521). > > Is this from a VM you built yourself? This is a VM built from source during packaging for NixOS Linux. What's the output of: > > $ pharo --version > Here it is: $ pharo-vm-nox --version 3.9-7 #1 Tue Mar 28 16:26:45 UTC 2017 gcc 5.4.0 [Production ITHB VM] NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Apr 5 2016 NBCogit NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Apr 5 2016 https://github.com/pharo-project/pharo-vm.git Commit: ba1aa855f546b084ec0ebdeb85a36f2352f97b49 Date: 2016-02-18 17:17:13 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #15040 Linux localhost 4.4.23 #1-NixOS SMP Fri Sep 30 08:20:43 UTC 2016 i686 GNU/Linux plugin path: /nix/store/5bm2pwrkd1083sb1f1rf0jz20cw87yya-pharo-vm-i386-2016.02.18/lib/pharo-vm-i386-2016.02.18/ [default: /nix/store/5bm2pwrkd1083sb1f1rf0jz20cw87yya-pharo-vm-i386-2016.02.18/lib/pharo-vm-i386-2016.02.18/] Note that the date 2016-02-18 corresponds with the latest non-spur source tarball release at http://files.pharo.org/vm/src/vm-unix-sources/ I just downloaded: > > $ curl http://get.pharo.org/50+vm | bash > > And it started without problem. > I *think* the difference is that you are downloading the VM as a binary and I am downloading it as source code, and we get different versions because pharo.org is regularly shipping updated binaries but not updating the source code releases at the same time. So the source releases lag behind over time and now it's at the point that they can't run the 5.0 image.

April 15, 2017

Re: [Pharo-users] Pharo 6 snap install

by Alistair Grant

On Sat, Apr 15, 2017 at 06:43:39AM +0200, Luke Gorrie wrote: > On 14 April 2017 at 22:20, 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. > > > It is possible that I have misunderstood the whole situation and there is no > problem at all. That would be awesome. Let's check :-) here is my understanding > of the state of the world right now: I think so... > The latest stable image release is Pharo-50771.image. > The latest stable VM source release is pharo-vm-2016.02.18. > These two releases are not compatible: This interpreter (vers. 6505) cannot > read image file (vers. 6521). Is this from a VM you built yourself? What's the output of: $ pharo --version I just downloaded: $ curl http://get.pharo.org/50+vm | bash And it started without problem. The VM is dated Wed May 4 11:54:28 CEST 2016. > So the problem is that if a distribution packages the latest VM source release > then the users won't be able to run the Pharo 5 VM that they download from > pharo.org or via the pharo-launcher image. > > Is that correct? If so that's fine and hopefully we can fix it for Pharo 6.0. > But if I am misunderstanding and a fix is available today that would also be > good to know. > > I am looking for the "latest VM source release" in http://files.pharo.org/vm/ > src/vm-unix-sources/ and assuming that non-spur is the stable option for > pre-6.0 images. Occasional bugs aside, my understanding is that V5.0 VMs will work with V5.0 images. They should at least start up OK. Cheers, Alistair

April 15, 2017

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

by Holger Freyther

> On 15. Apr 2017, at 07:59, Holger Freyther <holger(a)freyther.de> wrote: > > > * Why isn't the migration from Ston to Fuel more explicit? > * Why is "load" trying to save? > * Why is "ensure:" used instead of load? > * Not sure why "self preferences exists" seems to end in true? Is there an option to not run startUp options at all or single step through them? I have the suspicion that "exists" returns true while it should not. Will see how to move forward. holger Breakpoint 4, dir_EntryLookup (pathString=0x84cd258 "/home/build/.config/pharo", pathStringLength=25, nameString=0x84ce920 "org.pharo.gt.spotter.event.recorder.fuel", nameStringLength=40, name=0xfffcb1bc "", nameLength=0xfffcb1ac, creationDate=0xfffcb1a4, modificationDate=0xfffcb1b0, isDirectory=0xfffcb1a8, sizeIfFile=0xfffcb198, posixPermissions=0xfffcb1b4, isSymlink=0xfffcb1b8) at /home/travis/build/pharo-project/pharo-vm/opensmalltalk-vm/platforms/unix/plugins/FilePlugin/sqUnixFile.c:270 270 in /home/travis/build/pharo-project/pharo-vm/opensmalltalk-vm/platforms/unix/plugins/FilePlugin/sqUnixFile.c (gdb) p printCallStack() 0xfffd41a0 M UnixStore(DiskStore)>basicEntryAt: 0x842dd28: a(n) UnixStore 0xfffd41c0 M UnixStore(DiskStore)>nodeAt:ifPresent:ifAbsent: 0x842dd28: a(n) UnixStore 0xfffd41e4 M UnixStore(FileSystemStore)>exists: 0x842dd28: a(n) UnixStore 0xfffd4200 M FileSystem>exists: 0x842dd38: a(n) FileSystem 0xfffd421c M FileReference>exists 0x84c9d78: a(n) FileReference 0xfffd4234 M FileLocator(AbstractFileReference)>exists 0x84c32c8: a(n) FileLocator 0xfffd4254 I GlobalIdentifierFuelPersistence(GlobalIdentifierPersistence)>load: 0x84a6d40: a(n) GlobalIdentifierFuelPersistence 0xfffd4278 I GlobalIdentifierFuelPersistence(GlobalIdentifierPersistence)>ensure: 0x84a6d40: a(n) GlobalIdentifierFuelPersistence 0xfffd429c I GlobalIdentifierStonPersistence(GlobalIdentifierPersistence)>ensure: 0x84a6d30: a(n) GlobalIdentifierStonPersistence 0xfffd42c0 I GlobalIdentifier>ensure 0x84a6510: a(n) GlobalIdentifier 0xfffd42e0 I GlobalIdentifier class>initializeUniqueInstance 0x9a2def0: a(n) GlobalIdentifier class 0xfffd4300 I GlobalIdentifier class>uniqueInstance 0x9a2def0: a(n) GlobalIdentifier class 0xfffccfd0 I SystemSettingsPersistence class>resumeSystemSettings 0x9a2d9f0: a(n) SystemSettingsPersistence class

April 15, 2017

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

by Stephane Ducasse

Holger with guille, damien and two students we are looking at how to improve the deployment of pharo and you scenario is really interesting. Stef On Sat, Apr 15, 2017 at 7:59 AM, Holger Freyther <holger(a)freyther.de> wrote: > > > On 15. Apr 2017, at 00:23, Juraj Kubelka <juraj.kubelka(a)icloud.com> > wrote: > > > > Hi, > > Hey! > > >> 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. > > Thank you for your quick reply. What I find odd is that this error seems > to be coming from within: > > > GlobalIdentifierStonPersistence(GlobalIdentifierPersistence)>>ensure: > self shouldCallPreviousPersistence ifTrue: [ > previousPersistence ensure: existingDictionary ]. > > So there is the "Fuel" Persistence and we want to migrate things. Fair > enough but in the migration we do have: > > > >>load: existingDictionary > "It loads stored information into existingDictionary." > self preferences exists ifFalse: [ > "This is a new computer, so we define new computer UUID. > User still has to agree about sending data if it is not > has been done yet." > ^ self save: existingDictionary ]. > > > So self preferences exists is true and now the old (non-existent data?) is > being saved and we crash and exit on save. > > * Why isn't the migration from Ston to Fuel more explicit? > * Why is "load" trying to save? > * Why is "ensure:" used instead of load? > * Not sure why "self preferences exists" seems to end in true? > > > > have a nice weekend > > holger > > > > >> FileLocator(AbstractFileReference)>>ensureCreateDirectory > >> GlobalIdentifierFuelPersistence(GlobalIdentifierPersistence) > >>ensureDirectory > >> GlobalIdentifierFuelPersistence(GlobalIdentifierPersistence)>>save: > >> GlobalIdentifierFuelPersistence(GlobalIdentifierPersistence)>>load: > >> GlobalIdentifierFuelPersistence(GlobalIdentifierPersistence)>>ensure: > >> GlobalIdentifierStonPersistence(GlobalIdentifierPersistence)>>ensure: > >> GlobalIdentifier>>ensure > > > > >

April 15, 2017

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

by Nicolai Hess

2017-04-14 17:13 GMT+02:00 Hilaire <hilaire(a)drgeo.eu>: > 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) > > > > How to reproduce: "Create a Trait" Trait named:#TRoot uses:{} package:'MyPackage'. "Add some methods" (Smalltalk classOrTraitNamed:'TRoot') compile:'trootA'. (Smalltalk classOrTraitNamed:'TRoot') compile:'trootB'. (Smalltalk classOrTraitNamed:'TRoot') compile:'trootC'. "Create another Trait using this Trait" Trait named:#TRootUser uses:{(Smalltalk classOrTraitNamed:'TRoot')} package:'MyPackage'. "Add more methods. Note, methods still added on TRoot" (Smalltalk classOrTraitNamed:'TRoot') compile:'troot1'. (Smalltalk classOrTraitNamed:'TRoot') compile:'troot2'. (Smalltalk classOrTraitNamed:'TRoot') compile:'troot3'. "Trait TRootUser should not have any local methods" (RPackageOrganizer default packageNamed:'MyPackage') methods inspect. Exprected outcome: All methods are only defined on Trait TRoot. Actual outcome: Methods from TRoot added before creating the Trait that uses TRoot, are *added* to the using trait, but only in the RPackage, the trait, *using* TRoot still *knows* that it does not hold any local methods: TRootUser localMethods. -> "#()" TRoot localMethods -> "{TRoot>>#troot1. TRoot>>#troot3. TRoot>>#trootC. TRoot>>#trootB. TRoot>>#trootA. TRoot>>#troot2}" Now, if we store a snapshot of this package, the RGMethodDefinitions, wrongly assigned to trait TRootUser, will be flattened into that trait. > -- > Dr. Geo > http://drgeo.eu > > >

April 15, 2017

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

by Holger Freyther

> On 15. Apr 2017, at 00:23, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > > Hi, Hey! >> 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. Thank you for your quick reply. What I find odd is that this error seems to be coming from within: GlobalIdentifierStonPersistence(GlobalIdentifierPersistence)>>ensure: self shouldCallPreviousPersistence ifTrue: [ previousPersistence ensure: existingDictionary ]. So there is the "Fuel" Persistence and we want to migrate things. Fair enough but in the migration we do have: >>load: existingDictionary "It loads stored information into existingDictionary." self preferences exists ifFalse: [ "This is a new computer, so we define new computer UUID. User still has to agree about sending data if it is not has been done yet." ^ self save: existingDictionary ]. So self preferences exists is true and now the old (non-existent data?) is being saved and we crash and exit on save. * Why isn't the migration from Ston to Fuel more explicit? * Why is "load" trying to save? * Why is "ensure:" used instead of load? * Not sure why "self preferences exists" seems to end in true? have a nice weekend holger >> FileLocator(AbstractFileReference)>>ensureCreateDirectory >> GlobalIdentifierFuelPersistence(GlobalIdentifierPersistence)>>ensureDirectory >> GlobalIdentifierFuelPersistence(GlobalIdentifierPersistence)>>save: >> GlobalIdentifierFuelPersistence(GlobalIdentifierPersistence)>>load: >> GlobalIdentifierFuelPersistence(GlobalIdentifierPersistence)>>ensure: >> GlobalIdentifierStonPersistence(GlobalIdentifierPersistence)>>ensure: >> GlobalIdentifier>>ensure

April 15, 2017

Re: [Pharo-users] Pharo 6 snap install

by Luke Gorrie

On 14 April 2017 at 22:20, 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. > It is possible that I have misunderstood the whole situation and there is no problem at all. That would be awesome. Let's check :-) here is my understanding of the state of the world right now: The latest stable image release is Pharo-50771.image. The latest stable VM source release is pharo-vm-2016.02.18. These two releases are not compatible: This interpreter (vers. 6505) cannot read image file (vers. 6521). So the problem is that if a distribution packages the latest VM source release then the users won't be able to run the Pharo 5 VM that they download from pharo.org or via the pharo-launcher image. Is that correct? If so that's fine and hopefully we can fix it for Pharo 6.0. But if I am misunderstanding and a fix is available today that would also be good to know. I am looking for the "latest VM source release" in http://files.pharo.org/vm/src/vm-unix-sources/ and assuming that non-spur is the stable option for pre-6.0 images. Cheers! -Luke

April 15, 2017

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

Traits score: Squeak: 1, Pharo5: 0

by Hilaire

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

[ANN] Prometheas : a Pharo wiki database

by Dimitris Chloupis

Part of my Discord bot as a goal was to add the ability to create database entries so that people can quickly find documentation. It was quite a challenge for me because I had to learn how heroku works, PostgreSQL and all the other things but I did it!!! In any discord channel you have now 3 commands !doc , !docadd , !docremove 1) !doc <search_term> search for a term in the documentation database eg. !doc pharo 2) !docadd <search_term> <content> <tags> <links> add a new entry to the documentation database eg. !docadd "pharo" "Pharo is a modern implementation of Smalltalk" "{'smalltalk','live coding','language'}" "{'squeak','IDE'}" 3)!docremove <search_term> remove a term from database eg. !docremove pharo tags , is for more complex searches in the future, links for sending users to relevant documentation I am also planning to give access to pharo users to the database from inside the pharo image, if its easy enough to use PostgreSQL from inside Pharo. Currently the bot is fully coded in python. The goal is not to create a full documentation but rather quick help tips for fast pointing to the right direction. This is also an invite to experience pharo devs and newcomers to start adding to this database. The database is PostgreSQL , one of the most populars, I have nothing against MongoDB , its just that it works better with heroku where I host the database. But if in the future find a way to do it for free I can move to MongoDB, but no promises. Anyway this was an excuse for me to learn database programming that I had abandoned 25 years ago (DBASE). So have fun with this :)

April 14, 2017

Re: [Pharo-users] Traits, method flatten

by Hilaire

Ah, no my bad. Squeak was file in correctly the Trait and Class, it is just that its browser does not let you know if a method class belong to one of its Traits or the class itself Le 14/04/2017 Ã 11:16, Hilaire a Ã©crit : > Give a try to filein the correct .st source file of the Traits+Classes > package. It does not get it right :( > > Pharo5 get it right when loading the .st source file though. > > Still investigating... -- Dr. Geo http://drgeo.eu

April 14, 2017

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

by Stephane Ducasse

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