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

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

by Ben Coman

On Sat, Apr 15, 2017 at 3:11 PM, Holger Freyther <holger(a)freyther.de> wrote: > >> 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? Highly speculative... >From the command line compile a "self halt" into PharoCommandLineHandler>>activate cheers -ben > 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 16, 2017

Re: [Pharo-users] Pharo 6 snap install

by Ben Coman

Whoops, now copied to pharo-dev to continue discussion there. On Sun, Apr 16, 2017 at 9:13 PM, Ben Coman <btc(a)openinworld.com> wrote: > On Sat, Apr 15, 2017 at 12:43 PM, Luke Gorrie <luke(a)snabb.co> 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: >> >> 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. > > That is not correct. Pharo 5 used a Spur-VM since build 50496 circa 2015-12-14. > * http://files.pharo.org/image/50-preSpur/ > * http://files.pharo.org/image/50/ > > cheers -ben

April 16, 2017

Re: [Pharo-users] Pharo 6 snap install

by Ben Coman

On Sat, Apr 15, 2017 at 12:43 PM, Luke Gorrie <luke(a)snabb.co> 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: > > 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. That is not correct. Pharo 5 used a Spur-VM since build 50496 circa 2015-12-14. * http://files.pharo.org/image/50-preSpur/ * http://files.pharo.org/image/50/ cheers -ben

April 16, 2017

Re: [Pharo-users] Pharo image freeze and "Alt-." has no effect

by Stephane Ducasse

Steven welcome. I hope that you will make a great implementation. If you have a reproducible case where alt+ does not work we are interested. Denis improved the situation but we lack of a case that we can reproduce to improve it again. Stef On Sat, Apr 8, 2017 at 1:39 PM, Steven RÃ©mot <steven.remot(a)gmail.com> wrote: > It looks like the freeze is not present on the latest dev release Ben. I > will tell you if it just takes time to appear but it looks much more stable. > > Thanks! > Steven RÃ©mot > > Le sam. 8 avr. 2017 Ã 02:46, Ben Coman <btc(a)openinworld.com> a Ã©crit : > >> Just for starters, can you try with dev-latest VM & Image... >> * http://files.pharo.org/vm/pharo-spur32/linux/pharo-linux-i386threaded- >> 201704041239-b3f27b3.zip >> * http://files.pharo.org/image/60/60463.zip >> >> cheers -ben >> >> On Fri, Apr 7, 2017 at 7:05 PM, Steven RÃ©mot <steven.remot(a)gmail.com> >> wrote: >> >> I'm on Linux (Ubuntu 15.10), and the output of pharo -v is: >> >> 5.0 #1 Wed May 4 11:54:28 CEST 2016 gcc 4.6.3 [Production Spur ITHB VM] >> CoInterpreter VMMaker.oscog-eem.1855 uuid: d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 >> May 4 2016 >> StackToRegisterMappingCogit VMMaker.oscog-eem.1855 uuid: >> d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016 >> https://github.com/pharo-project/pharo-vm.git Commit: >> b8ec25a570d7539653e1d793e97609adb509aaed Date: 2016-05-04 11:14:22 +0200 >> By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #589 >> Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 16:39:45 >> UTC 2012 i686 i686 i386 GNU/Linux >> plugin path: /home/steven/Documents/Programmes/pharo5.0/bin [default: >> /home/steven/Documents/Programmes/pharo5.0/bin/] >> >> >> Le ven. 7 avr. 2017 Ã 12:54, Alistair Grant <akgrant0710(a)gmail.com> a >> Ã©crit : >> >> Hi Steven, >> >> Can you tell us which platform you're on, and the output of pharo >> --version >> >> Cheers, >> Alistair >> >> >> On 7 Apr. 2017 12:48, "Steven RÃ©mot" <steven.remot(a)gmail.com> wrote: >> >> Hello everyone, >> >> I'm new to pharo, and was writing a simple 2D game with Athens for >> rendering to practice a bit. I'm loving the environment so far, developing >> the game while it's running is really enjoyable :-) . >> >> However, when the game is running, the pharo image will freeze at a >> random time. Alt-. doesn't make my image back to normal, the only solution >> I found is closing my image and opening it again, until the next freeze... >> >> I don't really know what to do to investigate this bug, there is no >> output from pharo about this. The only thing I thought about is starting >> from a fresh image, importing my code and running it again to ensure it >> wasn't some messy state in the image I was using, and it froze even when >> running my code from a fresh image. >> >> What can I do to debug it? Do you need more information to give me a >> direction? >> >> Just in case you need it, here is the source: https://www.dropbox.com/s/ >> pfn7ccw27i4nqr7/Creakout-debug.st?dl=0 >> >> Thanks, >> Steven RÃ©mot >> >> >> >>

April 16, 2017

Re: [Pharo-users] FileReference / and parent

by Stephane Ducasse

Hi alistair I do not remember (may be I wrote this class comment because there were none and I got frustrated). So improving the class comments may be needed. Stef On Fri, Apr 7, 2017 at 10:31 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > On Fri, Apr 07, 2017 at 08:43:50PM +0200, Esteban Lorenzano wrote: > > > > > On 7 Apr 2017, at 20:30, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > > > > Hi Dennis, > > > > > > On Fri, Apr 07, 2017 at 10:58:57AM +0200, Denis Kudriashov wrote: > > >> Hi Alistair. > > >> > > >> Do you open the issue? > > >> I found that it was already exist. Look at 13217 > > >> <https://pharo.fogbugz.com/f/cases/13217/FS-basename-with- > compound-path-string> > > > > > > I haven't opened it yet - as you suggested in the issue, given how busy > > > Esteban and everyone is with getting Pharo 6 out the door, I'm waiting > > > for Pharo 7 dev to start. I've got the code and automated tests done, > > > although reading the issue has made me think that I should also review > > > the class comments. > > > > > > I'll add a comment to the issue and then submit the patch once the > Pharo > > > 7 inbox is open. > > > > that's very good... thank you very much! > > > > Esteban > > And of course, just after posting the proposed patch in the issue, I > found a bug with it. > > After re-reading the Path class comment I've also realised that my patch > breaks the explicit behaviour in the comment. But... > > The class comment in Path (I belive) is wrong. > > The class comment states that a slash (/) can be included in the file > name with "parent\/child\/", however it didn't work when I tried it, and > there are multiple answers in stackoverflow and stackexchange stating > that / and \0 (null character) are the two forbidden (ascii) characters > on linux. Windows includes / (slash), \ (backslash) and several others. > > Wikipedia has an article on it: > https://en.wikipedia.org/wiki/Filename#Reserved_characters_and_words > > From a purely practical point of view, I think trying to be completely > general (meaning allowing the directory separator in a filename) in this > case causes many more problems with unexpected behaviour than it solves, > so I still would like to see this changed in Pharo 7 (once I fix my > patch and extend the automated tests :-)). > > Cheers, > Alistair > >

April 16, 2017

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

by Stephane Ducasse

ok thanks On Sat, Apr 15, 2017 at 11:05 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I believe what you want is to start debugging a parser with some script > and then stepping through it. > > The SmaCC debugger only gets activated if the SmaCC code is in the > execution context. So, if you do not have it yet you can âStep to debuggerâ. > > For example: > - Try debugging: > JavaParser parse: 'public class A {}' > - Then from the window menu, choose âStep to debuggerâ / âSmaCCâ > - And you will get the SmaCC debugger > > Cheers, > Doru > > > > On Apr 15, 2017, at 2:34 PM, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > > John? How do we activate the Smacc debugger in moose? > > On Fri, Apr 14, 2017 at 10:36 PM, Andrei Chis <chisvasileandrei(a)gmail.com > > wrote: > 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 > > > > > -- > www.tudorgirba.com > www.feenk.com > > "Innovation comes in the least expected form. > That is, if it is expected, it already happened." > >

April 16, 2017

Re: [Pharo-users] PostgreSQL and Pharo 6

by Dimitris Chloupis

Thanks Sven, as always top quality blog post On Sun, 16 Apr 2017 at 12:04, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 16 Apr 2017, at 10:36, Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > > > > Hey guys , I play with PostgreSQL and I really like it, sorry Esteban :D > > > > I am using Python for it but I would like to give access also to Pharo > to my database. I was informed that Garage has a driver for PostgreSQL , is > there any other candidate ? Any advice ? > > There are basically just two drivers: the trusted V2 driver which is using > the traditional ASCII PostgreSQL protocol and the newer V3 driver which is > using the binary PostgreSQL protocol. That last one might be a bit less > supported by higher level packages, while the former has been around > forever. > > These drivers are pretty low level. > > If you want higher level access, there is of course Glorp, a very good > OO-RDBMS mapper. > > For a short intro, you could read the following article: > > > https://medium.com/concerning-pharo/reddit-st-in-10-cool-pharo-classes-1b53… > > Sven >

April 16, 2017

Re: [Pharo-users] PostgreSQL and Pharo 6

by Sven Van Caekenberghe

> On 16 Apr 2017, at 10:36, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > Hey guys , I play with PostgreSQL and I really like it, sorry Esteban :D > > I am using Python for it but I would like to give access also to Pharo to my database. I was informed that Garage has a driver for PostgreSQL , is there any other candidate ? Any advice ? There are basically just two drivers: the trusted V2 driver which is using the traditional ASCII PostgreSQL protocol and the newer V3 driver which is using the binary PostgreSQL protocol. That last one might be a bit less supported by higher level packages, while the former has been around forever. These drivers are pretty low level. If you want higher level access, there is of course Glorp, a very good OO-RDBMS mapper. For a short intro, you could read the following article: https://medium.com/concerning-pharo/reddit-st-in-10-cool-pharo-classes-1b53… Sven

April 16, 2017

PostgreSQL and Pharo 6

by Dimitris Chloupis

Hey guys , I play with PostgreSQL and I really like it, sorry Esteban :D I am using Python for it but I would like to give access also to Pharo to my database. I was informed that Garage has a driver for PostgreSQL , is there any other candidate ? Any advice ?

April 16, 2017

Re: [Pharo-users] why is adding instance variables so slow?

by Tudor Girba

Hi, Please letâs move this discussion on pharo-dev. And keep going :) Cheers, Doru > On Apr 14, 2017, at 12:09 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > > 2017-04-14 11:09 GMT+02:00 tesonep(a)gmail.com <tesonep(a)gmail.com>: > Hi, I think the problem was not clearly explained. This is the scenario that is problematic. > This scenario does not happen in the new Spur implementation of forwarding, but I think is happening in the old one. > > 1. You have, let's say 3 instances of ClassA. > 2. You add a new instance variable to ClassA. It produces > 2a. A new ClassAv2 is created with the instances variables of ClassA and the newone > 2b. 3 Instances of ClassAv2 are created > 2c. The values of the instance variables of ClassA are copied to the ones in ClassAv2 (the ones missing are left in nil). > 2d. The 3 instances of ClassA are becomed forward to the 3 instances of ClassAv2 > 2e. The ClassA is becomed forward ClassAv2 > > I still not see why my example not reflects all these steps. I checked also scenario with class becoming: > > c1 := Class1 new. > c2 := Class2 new. > c1 becomeForward: c2. > Class1 becomeForward: Class2. > Class2 allInstances "=>#(aClass2)" > > It also works in Cog -- www.tudorgirba.com www.feenk.com "What we can governs what we wish."

April 16, 2017