- Pharo-users - lists.pharo.org

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