- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Seaside-dev] How should I load Seaside/Bootstrap in Pharo 7 ?
by Sven Van Caekenberghe Feb. 10, 2018

Feb. 10, 2018

Hi Maximiliano, I finally managed to reproduce your situation, using get.pharo.org/70+vm on Linux (Ubuntu 16.04.3 LTS, 64bit using a 32bit VM). Indeed the second time the image comes up blank. It does however still work (I had a running server in it and I could access it via the browser). You can also interrupt Pharo (ctrl-.) and the debugger shows the process is blocked at the 'wait wait' in the following method: SessionManager>>#snapshot: save andQuit: quit | isImageStarting wait | "We do the snapshot in a separate process in maximum priority to have always a clean startup. This process will be interrupted by the fork, and will be resumed as soon as the snapshot finishes. We synchronize these processes in case both are in the same priority. When both arguments are false, do nothing and return false." (save or: [quit]) ifFalse: [ ^ false ]. wait := Semaphore new. [ isImageStarting := self launchSnapshot: save andQuit: quit. wait signal ] forkAt: Processor highestPriority. wait wait. ^ isImageStarting Now, the underlying error is ZnCrPortableWriteStream that disappeared and is used by the command line handlers. It seems the latest Zinc (as loaded by Seaside) does not yet contain this class. I'll check and come back. Sven > On 9 Feb 2018, at 00:04, Maximiliano Tabacman via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Maximiliano Tabacman <mtabacman(a)yahoo.com> > Subject: Re: [Pharo-dev] [Seaside-dev] How should I load Seaside/Bootstrap in Pharo 7 ? > Date: 9 February 2018 at 00:04:59 GMT+1 > To: pharo-dev(a)lists.pharo.org, "Sean P. DeNigris" <sean(a)clipperadams.com> > > > I can only test it in Ubuntu and Windows for the moment. > > Steps to reproduce (in Windows) > 1) Download: > http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201802072244-997e… > 2) Download: > http://files.pharo.org/image/70/Pharo-7.0.0-alpha.build.512.sha.881c01b.arc… > 3) Unzip everything to the same directory, then start Pharo.exe > 4) Execute in Workspace > Metacello new > baseline:'Seaside3'; > repository: 'github://SeasideSt/Seaside:master/repository'; > load > 5) Save and Quit > 6) Try to start Pharo.exe > > If I delete stderr, stdout and PharoDebug.log before restarting Pharo, I can see that stderr and PharoDebug.log are created at 0 bytes, there is no other log that I can find. > > As you can see, no startup scripts are involved. This is a clean Pharo installation. And this happens both in Windows and in Ubuntu, no matter in which OS I try to do the download+load. > > If it is of any help, this has been happening exactly since build 383. It worked perfectly up to build 382. > On Thursday, February 8, 2018, 4:42:36 PM GMT-3, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > > Pharo Smalltalk Developers mailing list wrote > > I have no idea why this is happening > > I had a similar situation due to a deprecation warning generated by my > startup script. I aborted from the debugger, and the image worked normally, > but when I saved, quit and tried to restart the image, it wouldn't open (VM > icon in list of active apps, but window never appeared macOS high Sierra). > > > > > ----- > Cheers, > > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > > > >

2 2

Calypso wishlist
by Stephane Ducasse Feb. 9, 2018

Feb. 9, 2018

Hi denis - I would like to be able to define a method even in the class pane and that the system detects it automatically. - Then we are starting to reverse engineering the ecompletion system and I'm learning it. I would like to know if Calypso can communicate with ecompletion the fact that we are defining a method. Then I have to check how the system can know that we are typing method argument when defining the signature but I think that this is not related to calypso. Stef

4 7

[Pharo 7.0-dev] Build #516: 21258-Add-an-option-do-disable-WorldMorphs-drag-and-drop-for-deployment
by ci-pharo-ci-jenkins2＠inria.fr Feb. 9, 2018

Feb. 9, 2018

There is a new Pharo build available! The status of the build #516 was: SUCCESS. The Pull Request #815 was integrated: "21258-Add-an-option-do-disable-WorldMorphs-drag-and-drop-for-deployment" Pull request url: https://github.com/pharo-project/pharo/pull/815 Issue Url: https://pharo.fogbugz.com/f/cases/21258 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #515: 21256-Deprecated-glmSubscriptions-is-used-in-GLMBrickPropertiesTrait
by ci-pharo-ci-jenkins2＠inria.fr Feb. 9, 2018

Feb. 9, 2018

There is a new Pharo build available! The status of the build #515 was: FAILURE. The Pull Request #813 was integrated: "21256-Deprecated-glmSubscriptions-is-used-in-GLMBrickPropertiesTrait" Pull request url: https://github.com/pharo-project/pharo/pull/813 Issue Url: https://pharo.fogbugz.com/f/cases/21256 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #514: 21252-Add-method-comments-to-SUnit
by ci-pharo-ci-jenkins2＠inria.fr Feb. 9, 2018

Feb. 9, 2018

There is a new Pharo build available! The status of the build #514 was: FAILURE. The Pull Request #812 was integrated: "21252-Add-method-comments-to-SUnit" Pull request url: https://github.com/pharo-project/pharo/pull/812 Issue Url: https://pharo.fogbugz.com/f/cases/21252 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #510: 21246-Store-main-window-title
by ci-pharo-ci-jenkins2＠inria.fr Feb. 9, 2018

Feb. 9, 2018

There is a new Pharo build available! The status of the build #510 was: FAILURE. The Pull Request #809 was integrated: "21246-Store-main-window-title" Pull request url: https://github.com/pharo-project/pharo/pull/809 Issue Url: https://pharo.fogbugz.com/f/cases/21246 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

3 3

[Pharo 7.0-dev] Build #513: 21251-Improve-Senders-of
by ci-pharo-ci-jenkins2＠inria.fr Feb. 8, 2018

Feb. 8, 2018

There is a new Pharo build available! The status of the build #513 was: SUCCESS. The Pull Request #810 was integrated: "21251-Improve-Senders-of" Pull request url: https://github.com/pharo-project/pharo/pull/810 Issue Url: https://pharo.fogbugz.com/f/cases/21251 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] [Seaside-dev] How should I load Seaside/Bootstrap in Pharo 7 ?
by Sean P. DeNigris Feb. 8, 2018

Feb. 8, 2018

Pharo Smalltalk Developers mailing list wrote > I have no idea why this is happening I had a similar situation due to a deprecation warning generated by my startup script. I aborted from the debugger, and the image worked normally, but when I saved, quit and tried to restart the image, it wouldn't open (VM icon in list of active apps, but window never appeared macOS high Sierra). ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 1

[Pharo 7.0-dev] Build #512: 21254-Command-line-handlers-should-have-an-option-to-force-the-omission-of-preferences-for-applications-deployment
by ci-pharo-ci-jenkins2＠inria.fr Feb. 8, 2018

Feb. 8, 2018

There is a new Pharo build available! The status of the build #512 was: SUCCESS. The Pull Request #811 was integrated: "21254-Command-line-handlers-should-have-an-option-to-force-the-omission-of-preferences-for-applications-deployment" Pull request url: https://github.com/pharo-project/pharo/pull/811 Issue Url: https://pharo.fogbugz.com/f/cases/21254 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] [OpenSmalltalk/opensmalltalk-vm] Crashes while typing on macOS Sierra (#141)
by Eliot Miranda Feb. 8, 2018

Feb. 8, 2018

Hi Tobias, > On Feb 6, 2018, at 4:43 AM, Tobias Pape <notifications(a)github.com> wrote: > > Closed #141 via ecd41af. > thank you very much for this fix! Lots of people have been hurting from this. > â > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub, or mute the thread. >

2 2