December 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pharo image don't restart

by Ben Coman

On Thu, 13 Dec 2018 at 18:04, Trussardi Dario Romano < dario.trussardi(a)tiscali.it> wrote: > Ciao, > > You don't mention that you rebooted, so just try that first. > > > sorry but I do not understand what you mean. > > In any case i rebooted the system. ( restart ) > Yes, thats what I meant. Always the easiest thing to try. > > The PharoLauncher launch command on the Pharo 7.0 -64development image report > the same error. > > >> * I have some important work in the image ( and i don't have a backup ) >> Some consideration?* >> > I'm not in a position to diagnose the error, but perhaps help you recover your work. In PharoLauncher, if you right-click on the image you are trying to launch, then choose "Show in folder" then browse to "pharo-local/ombu-sessions" and you should see some files. If you create a fresh image and copy those to the same location there, the go World menu > Tools > Code Changes and see if you find your work. Check out the filters. Possibly useful... * Show only latest changes * Show only changes in this package HTH cheers -ben

Dec. 13, 2018

Re: [Pharo-dev] Pharo image don't restart

by Trussardi Dario Romano

Ciao, > You don't mention that you rebooted, so just try that first. sorry but I do not understand what you mean. In any case i rebooted the system. ( restart ) The PharoLauncher launch command on the Pharo 7.0 -64development image report the same error. Thanks, Dario > > cheers -ben > > P.S. Quick summary for others, the error is... > "no room in eden for allocateSmallNewSpaceSlots:format:classIndex:" > > Top of Smalltalk stack dump: > 0x7ffeec4c4a88 I ExternalSemaphoreTable class>unprotectedExternalObjects: 0x1d044b0: a(n) ExternalSemaphoreTable class > 0x7ffeec4c4ad0 I [] in ExternalSemaphoreTable class>clearExternalObjects 0x1d044b0: a(n) ExternalSemaphoreTable class > 0x7ffeec4c4b20 I [] in Semaphore>critical: 0x211ec80: a(n) Semaphore > 0x7ffeec4c4b70 I BlockClosure>ensure: 0x165e2d0: a(n) BlockClosure > 0x7ffeec4c4bc0 I Semaphore>critical: 0x211ec80: a(n) Semaphore > 0x7ffeec4c4c08 I ExternalSemaphoreTable class>clearExternalObjects 0x1d044b0: a(n) ExternalSemaphoreTable class > 0x7ffeec4c4c48 I SmalltalkImage>clearExternalObjects 0x1d0a920: a(n) SmalltalkImage > 0x7ffeec4c4c88 I WorkingSession>start: 0x165e000: a(n) WorkingSession > 0x7ffeec4c4ce0 I SessionManager>launchSnapshot:andQuit: 0x1d70a10: a(n) SessionManager > 0xbff6c50 s SessionManager>snapshot:andQuit: > 0xc006a18 s [] in SmalltalkImage>snapshot:andQuit: > > > > On Thu, 13 Dec 2018 at 16:26, Trussardi Dario Romano <dario.trussardi(a)tiscali.it> wrote: > Ciao, > > i have a Ubuntu system > where i defined a Pharo 7.0 - 64bit image managed with PharoLauncher. > > I work with it for a month and all work fine. > > Now after a save the image the system begin unstabled. > > When the mouse go on the windows summary bar ( at the bottom of the Pharo window ) the image go down. > > The first time i can launch the same image from the PharoLauncher, > > but after a new image save ( the image go down ) i can't relaunch the image. > > When i do the launch the pharoLauch shell report: > > > I have some important work in the image ( and i don't have a backup ) > > Some consideration? > > Thanks, > Dario >

Dec. 13, 2018

Re: [Pharo-dev] Pharo image don't restart

by Ben Coman

You don't mention that you rebooted, so just try that first. cheers -ben P.S. Quick summary for others, the error is... "no room in eden for allocateSmallNewSpaceSlots:format:classIndex:" Top of Smalltalk stack dump: 0x7ffeec4c4a88 I ExternalSemaphoreTable class>unprotectedExternalObjects: 0x1d044b0: a(n) ExternalSemaphoreTable class 0x7ffeec4c4ad0 I [] in ExternalSemaphoreTable class>clearExternalObjects 0x1d044b0: a(n) ExternalSemaphoreTable class 0x7ffeec4c4b20 I [] in Semaphore>critical: 0x211ec80: a(n) Semaphore 0x7ffeec4c4b70 I BlockClosure>ensure: 0x165e2d0: a(n) BlockClosure 0x7ffeec4c4bc0 I Semaphore>critical: 0x211ec80: a(n) Semaphore 0x7ffeec4c4c08 I ExternalSemaphoreTable class>clearExternalObjects 0x1d044b0: a(n) ExternalSemaphoreTable class 0x7ffeec4c4c48 I SmalltalkImage>clearExternalObjects 0x1d0a920: a(n) SmalltalkImage 0x7ffeec4c4c88 I WorkingSession>start: 0x165e000: a(n) WorkingSession 0x7ffeec4c4ce0 I SessionManager>launchSnapshot:andQuit: 0x1d70a10: a(n) SessionManager 0xbff6c50 s SessionManager>snapshot:andQuit: 0xc006a18 s [] in SmalltalkImage>snapshot:andQuit: On Thu, 13 Dec 2018 at 16:26, Trussardi Dario Romano < dario.trussardi(a)tiscali.it> wrote: > > > > > > > > *Ciao, i have a Ubuntu system where i defined a Pharo 7.0 - 64bit image > managed with PharoLauncher. I work with it for a month and all work fine. > Now after a save the image the system begin unstabled. When the mouse go on > the windows summary bar ( at the bottom of the Pharo window ) the image go > down. The first time i can launch the same image from the PharoLauncher, > but after a new image save ( the image go down ) i can't relaunch the > image. When i do the launch the pharoLauch shell report:* > > > > > > > * I have some important work in the image ( and i don't have a backup ) > Some consideration? Thanks, Dario* >

Dec. 13, 2018

Re: [Pharo-dev] Application entrypoints

by nanqueti

we could also use the "script:" annotation, and the system browser could show it at the class level (it already shows at the method level) nicolas On Thu, 2018-12-13 at 10:40 +0800, Ben Coman wrote: > A question was asked on discord... "I know how to start the lights > out example, > and feed my objects test data with the testing framework, but how > does one start > something like ChineseCheckers? How does one find the entry point? > Is there a convention on naming a starting place?" > > I remember having similar thoughts when starting in Pharo. > > One convention I have seen is that amongst all the classes presumably > prefixed "CC" > one class would stand out being named for the application without the > prefix. > e.g. class "ChineseCheckers". That is only a narrow chance for a > namespace conflict, > the the risk still remains. > > I suggested another path would have a package tag "Application" > (i.e. "ChineseCheckers-Application") that contains a single class > which has an #open method on the class-side. > The tag "Application" sorts high up on the package-tags and is self- > descriptive. > But I've not seen that used before, so while I think its a good idea, > its not really a convention. > Conventions are only useful if they are broadly understood. > > So I'm wondering what other things people do to draw attention to > their application entry points. > > cheers -ben -- Nicolas Anquetil RMod team -- Inria Lille

Dec. 13, 2018

Pharo image don't restart

by Trussardi Dario Romano

Ciao, i have a Ubuntu system where i defined a Pharo 7.0 - 64bit image managed with PharoLauncher. I work with it for a month and all work fine. Now after a save the image the system begin unstabled. When the mouse go on the windows summary bar ( at the bottom of the Pharo window ) the image go down. The first time i can launch the same image from the PharoLauncher, but after a new image save ( the image go down ) i can't relaunch the image. When i do the launch the pharoLauch shell report: I have some important work in the image ( and i don't have a backup ) Some consideration? Thanks, Dario

Dec. 13, 2018

Application entrypoints

by Ben Coman

A question was asked on discord... "I know how to start the lights out example, and feed my objects test data with the testing framework, but how does one start something like ChineseCheckers? How does one find the entry point? Is there a convention on naming a starting place?" I remember having similar thoughts when starting in Pharo. One convention I have seen is that amongst all the classes presumably prefixed "CC" one class would stand out being named for the application without the prefix. e.g. class "ChineseCheckers". That is only a narrow chance for a namespace conflict, the the risk still remains. I suggested another path would have a package tag "Application" (i.e. "ChineseCheckers-Application") that contains a single class which has an #open method on the class-side. The tag "Application" sorts high up on the package-tags and is self-descriptive. But I've not seen that used before, so while I think its a good idea, its not really a convention. Conventions are only useful if they are broadly understood. So I'm wondering what other things people do to draw attention to their application entry points. cheers -ben

Dec. 13, 2018

Re: [Pharo-dev] periodic auto actions on bug tracker

by Sean P. DeNigris

Marcus Denker-4 wrote >> I support the auto-closing of old tickets to avoid bug bankruptcy > ... > Yes, that is a good idea. I thought we already did that. Don't we even have a stale/timeout tag to distinguish from other reasons for closing and help find them again later if needed? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 13, 2018

Re: [Pharo-users] [ANN] Pharo Newsletter December 2018

by Alexandre Bergel

Hi Marcus! Maybe a news about the first 6 chapters of Agile Artificial Intelligence. https://agileartificialintelligence.github.io/ Cheers Alexandre http://bergel.eu > Le 12 dÃ©c. 2018 Ã 05:17, Marcus Denker <marcus.denker(a)inria.fr> a Ã©crit : > > > >> On 11 Dec 2018, at 14:08, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Hi, >> >> Last we the Pharo Newsletter December 2018 was send. >> >> You can find the archived version now here: >> >> https://mailchi.mp/pharo/pharo-newsletter-december-2018 >> > > I am looking for content for the January newsletter. > > e.g. if you know a library that has not yet been listed, or just one where some new version has been released. > Or people could write âlargerâ articles (a paragraph or two) about their favourite things. > > Or maybe there are videos that would be nice to be added to the newsletter? > > Marcus

Dec. 13, 2018

Re: [Pharo-users] [ANN] Git Thermite integration with Iceberg

by Alexandre Bergel

It would be really great to have feedback. Please, providing feedback is key to enable innovation in this community! Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Dec 12, 2018, at 12:21 PM, Ronie Salgado <roniesalg(a)gmail.com> wrote: > > Hello, > > Some time ago I presented Git Thermite in this mailing. Git Thermite is a tool for visualizing Git commits that I am making for my master thesis. Now I have managed to integrate Git Thermite with Iceberg. > > GitHub page: https://github.com/ronsaldo/pharo-git-thermite <https://github.com/ronsaldo/pharo-git-thermite> > Demo video: https://www.youtube.com/watch?v=TdBHpdyFgZE <https://www.youtube.com/watch?v=TdBHpdyFgZE> > Visualization learning material: https://github.com/ronsaldo/pharo-git-thermite/blob/master/doc/learning-mat… <https://github.com/ronsaldo/pharo-git-thermite/blob/master/doc/learning-mat…> > Feedback: https://docs.google.com/forms/d/e/1FAIpQLSeir6VlE3bR78oRsNAp9eHLkUn2Q016wEl… <https://docs.google.com/forms/d/e/1FAIpQLSeir6VlE3bR78oRsNAp9eHLkUn2Q016wEl…> > > Pharo 7 installation doIt: > > Metacello new > baseline: 'Thermite'; > repository: 'github://ronsaldo/pharo-git-thermite/src'; > load > Please, I would love to get some usage feedback through the Google form :-) > > Best regards, > Ronie

Dec. 12, 2018

[Pharo 7.0] Build #34: 22753-RBParseErrorNode-should-pretty-print-the-faulty-text-if-it-has-it

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #34 was: SUCCESS. The Pull Request #2061 was integrated: "22753-RBParseErrorNode-should-pretty-print-the-faulty-text-if-it-has-it" Pull request url: https://github.com/pharo-project/pharo/pull/2061 Issue Url: https://pharo.fogbugz.com/f/cases/22753 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 12, 2018