- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] external semaphoresâ¦again

by Henrik Johansen

On Oct 7, 2013, at 11:16 , Norbert Hartl <norbert(a)hartl.name> wrote: > As I need an image that runs longer than 24 hours I'm looking at some stuff and wonder. Can anybody explain me the rationale for a code like this > > maxExternalSemaphores: aSize > "This method should never be called as result of normal program > execution. If it is however, handle it differently: > - In development, signal an error to promt user to set a bigger size > at startup immediately. > - In production, accept the cost of potentially unhandled interrupts, > but log the action for later review. > > See comment in maxExternalObjectsSilently: why this behaviour is > desirable, " > "Can't find a place where development/production is decided. > Suggest Smalltalk image inProduction, but use an overridable temp > meanwhile. " > | inProduction | > self maxExternalSemaphores > ifNil: [^ 0]. > inProduction := false. > ^ inProduction > ifTrue: [self maxExternalSemaphoresSilently: aSize. > self crTrace: 'WARNING: Had to increase size of semaphore signal handling table due to many external objects concurrently in use'; > crTrace: 'You should increase this size at startup using #maxExternalObjectsSilently:'; > crTrace: 'Current table size: ' , self maxExternalSemaphores printString] > ifFalse: ["Smalltalk image" > self error: 'Not enough space for external objects, set a larger size at startup!' > "Smalltalk image"] > > I have reported this once but got no feedback so I like to have a few opinions. > > The report is here: https://pharo.fogbugz.com/f/cases/10839/ > > Norbert The rationale is that inProduction would be some global setting, not yet in place when the code was writtenâ¦ Excessive simultaneous Semaphore usage is something that should be caught during development, in which case it's better to get an active notification, than having it logged somewhere. If I've understood correctly, it's moot on newer Pharo VM's, where there's no limit on the semtable size, but for legacy code a startup item setting size using maxExternalObjectsSilently: (as suggested in the Warning text), is still a more proper fix than setting inProduction to true and crossing your fingers hoping no signals will be lost during table growth. Cheers. Henrik

Oct. 7, 2013

Re: [Pharo-dev] Please try to reproduce this bug

by Norbert Hartl

I have a lot of issues that this or like this. I get the sources problem as well as images I work for some time tell me that my working directory doesn't exist. I need to save and reopen the image to be able to do anything. Norbert Am 07.10.2013 um 10:12 schrieb Damien Cassou <damien.cassou(a)gmail.com>: > Can you please try to reproduce this bug: > > 1- Open a fresh Pharo 2.0 > 2- Open Monticello > 3- Select the package AST-Core > 4- Click browse > > you get a "PharoV20.sources does not exist." error message. You can't escape. > > Please write your findings in > https://pharo.fogbugz.com/f/cases/11803/PharoV20-sources-does-not-exist-whe…. > > For me, it looks like the problem is in MCPackage>>snapshot > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

Oct. 7, 2013

100% CPU usage on image resume

by Holger Hans Peter Freyther

Hi, I saved an image and today I wanted to resume it. Everything comes up, for a second I can interact with it (e.g. move a window) but then the pharo VM goes to 100% CPU usage. I let it run while writing this email and it eventually aborted: C stack backtrace: ./pharo[0x80a0c0c] ./pharo(error+0x19)[0x80a0f69] ./pharo[0x80785d3] ./pharo[0x80786e1] ./pharo[0x8078f10] ./pharo[0x8090d97] ./pharo(ceStackOverflow+0x6a)[0x80946ea] [0x76ef122e] ./pharo(interpret+0x7a6)[0x8094f36] ./pharo(main+0x2b3)[0x80a18b3] /lib/i386-linux-gnu/i686/cmov/libc.so.6(__libc_start_main+0xf5)[0xb74bb8c5] Smalltalk stack dump: 0xbfd5c610 M SmallInteger(Number)>negative 0x3841=7200 0xbfd5c630 M SmallInteger(Integer)>* 0x3841=7200 0xbfd5c64c M SmallInteger>* 0x3841=7200 0xbfd5c668 M Duration>asNanoSeconds 0x790ddef4: a(n) Duration 0xbfd5c684 M Duration>= 0x7fe004a0: a(n) Duration 0xbfd5c6a0 M DateAndTime>asLocal 0x7fe00488: a(n) DateAndTime 0xbfd5c6c0 M DateAndTime>- 0x7fe0040c: a(n) DateAndTime 0xbfd5c6dc M DateAndTime>asSeconds 0x7fe0040c: a(n) DateAndTime 0xbfd5c700 M DateAndTime>< 0x78d2a5f8: a(n) DateAndTime 0xbfd5c71c M DateAndTime(Magnitude)>> 0x7fe0040c: a(n) DateAndTime 0xbfd5c73c M TimerScheduler>fireTimers: 0x77ef49ac: a(n) TimerScheduler 0xbfd5c764 I [] in TimerScheduler>runTimers 0x77ef49ac: a(n) TimerScheduler 0xbfd5c780 M BlockClosure>on:do: 0x78d2a60c: a(n) BlockClosure 0xbfd5c7a4 M [] in Dispatcher>dispatch 0x77ef4764: a(n) Dispatcher 0xbfd5c7c4 M BlockClosure>ensure: 0x78d2a798: a(n) BlockClosure 0xbfd5c7f0 I [] in Dispatcher>dispatch 0x77ef4764: a(n) Dispatcher 0xbfd5c810 I [] in BlockClosure>newProcess 0x78d2a634: a(n) BlockClosure Most recent primitives stack page bytes 4096 available headroom 3300 minimum unused headroom 3508 (last object overwritten) Aborted TimerScheduler/Dispatcher is code of mine but I wouldn't understand why this code is getting blocked and would eventually cause a stack overflow? holger

Oct. 7, 2013

external semaphoresâ¦again

by Norbert Hartl

As I need an image that runs longer than 24 hours I'm looking at some stuff and wonder. Can anybody explain me the rationale for a code like this maxExternalSemaphores: aSize "This method should never be called as result of normal program execution. If it is however, handle it differently: - In development, signal an error to promt user to set a bigger size at startup immediately. - In production, accept the cost of potentially unhandled interrupts, but log the action for later review. See comment in maxExternalObjectsSilently: why this behaviour is desirable, " "Can't find a place where development/production is decided. Suggest Smalltalk image inProduction, but use an overridable temp meanwhile. " | inProduction | self maxExternalSemaphores ifNil: [^ 0]. inProduction := false. ^ inProduction ifTrue: [self maxExternalSemaphoresSilently: aSize. self crTrace: 'WARNING: Had to increase size of semaphore signal handling table due to many external objects concurrently in use'; crTrace: 'You should increase this size at startup using #maxExternalObjectsSilently:'; crTrace: 'Current table size: ' , self maxExternalSemaphores printString] ifFalse: ["Smalltalk image" self error: 'Not enough space for external objects, set a larger size at startup!' "Smalltalk image"] I have reported this once but got no feedback so I like to have a few opinions. The report is here: https://pharo.fogbugz.com/f/cases/10839/ Norbert

Oct. 7, 2013

Tracking smalltalk database driver implementations

by Guillermo Polito

Hi guys! I'm tracking the smalltalk implementations of relational database drivers that are floating around :). So far I have: * http://smalltalkhub.com/mc/PharoExtras/PostgresV2/main* Open source - last commit 2013 - This is the only one we use in DBXTalk with glorp. *http://www.squeaksource.com/MySQL.html* Does not specify licence - last commit around 2012 *http://www.squeaksource.com/PostgresV3.html* MIT licence - last commit around 2010 *http://www.squeaksource.com/ODBC.html* MIT licence - last commit around 2011 http://www.squeaksource.com/SQLite.html * http://ss3.gemstone.com/ss/SQLite.html/Overview?_s=kR2mf_G3WE3A6p9g&_k=I7aw… * MIT licence Now, except for postgresv2, all the others are in squeaksource. I'd like to move them to smalltalkhub under some "RelationalDatabase" group, maybe DBXTalk. But at the same time I imagine they are not pharo specific, ideas?

Oct. 7, 2013

Re: [Pharo-dev] Please try to reproduce this bug

by Goubier Thierry

In short: does not happens if you use the get.pharo.org vm. Happens if you use the ubuntu pharo ppa. (ubuntu 13.04 64bits) Thierry Le 07/10/2013 10:12, Damien Cassou a Ã©crit : > Can you please try to reproduce this bug: > > 1- Open a fresh Pharo 2.0 > 2- Open Monticello > 3- Select the package AST-Core > 4- Click browse > > you get a "PharoV20.sources does not exist." error message. You can't escape. > > Please write your findings in > https://pharo.fogbugz.com/f/cases/11803/PharoV20-sources-does-not-exist-whe…. > > For me, it looks like the problem is in MCPackage>>snapshot > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Oct. 7, 2013

Re: [Pharo-dev] Please try to reproduce this bug

by Goubier Thierry

I had this issue in many different situations in 2.0 late last week. Solved it by reverting to the get.pharo.org/20+vm instead of the ubuntu one. Thierry Le 07/10/2013 10:12, Damien Cassou a Ã©crit : > Can you please try to reproduce this bug: > > 1- Open a fresh Pharo 2.0 > 2- Open Monticello > 3- Select the package AST-Core > 4- Click browse > > you get a "PharoV20.sources does not exist." error message. You can't escape. > > Please write your findings in > https://pharo.fogbugz.com/f/cases/11803/PharoV20-sources-does-not-exist-whe…. > > For me, it looks like the problem is in MCPackage>>snapshot > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Oct. 7, 2013

Fwd: [ci-announces] Deployment of a new version

by Marcus Denker

Begin forwarded message: > Subject: [ci-announces] Deployment of a new version > Date: October 7, 2013 10:42:54 AM GMT+02:00 > To: ci-announces(a)inria.fr > > Dear users, > > A new version of the continuous integration service will be deployed > soon. You may experience issues today, do not hesitate to report them > on ci-support(a)inria.fr. >

Oct. 7, 2013

Re: [Pharo-dev] about creating Morphic-Widgets

by Pavel Krivanek

What about to try to make an update of the uMorphic experiment and place selected classes to the standalone package? http://forum.world.st/little-uMorphic-progress-td3762931.html We firstly needed to rename Morphic package to Morphic-Base but it is already done. Cheers, -- Pavel 2013/10/6 Tudor Girba <tudor(a)tudorgirba.com>: > +1 > > Doru > > > On Sun, Oct 6, 2013 at 10:28 PM, Benjamin > <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: >> >> I am in for splitting Morphic in more that one package. >> >> It makes things really boring to have every thing in one MC Package :( >> >> Ben >> >> On Oct 6, 2013, at 8:54 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> wrote: >> >> Hi guys >> >> I started to play with sorting a bit Morphic :) >> So I would like to create a new Package Morphics-Widgets with the >> following contents. >> >> >> Morphic-Widgets-Basic >> SimpleSwitchMorph >> MulticolumnLazyListMorph >> SimpleButtonMorph >> LazyListMorph >> IconicButton >> ThreePhaseButtonMorph >> CalendarMorph >> Morphic-Widgets-Pluggable >> PluggableTabButtonMorph >> PluggableButtonMorph >> PluggableTextMorph >> PluggableMultiColumnListMorph >> PluggableTextMorphWithLimits >> PluggableTabBarMorph >> PluggableListMorph >> Morphic-Widgets-NewList >> NewList >> NewListRenderer >> NewListAdapter >> Morphic-Widgets-Tab >> >> Morphic-Widget-MorphTreeWidget >> Morphic-Widget-MorphTreeWidget-Pagination >> >> I would promote Morphic-Base-ProgressBar -> Morphic-ProgressBar >> >> So what do you think? >> >> >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Oct. 7, 2013

Please try to reproduce this bug

by Damien Cassou

Can you please try to reproduce this bug: 1- Open a fresh Pharo 2.0 2- Open Monticello 3- Select the package AST-Core 4- Click browse you get a "PharoV20.sources does not exist." error message. You can't escape. Please write your findings in https://pharo.fogbugz.com/f/cases/11803/PharoV20-sources-does-not-exist-whe…. For me, it looks like the problem is in MCPackage>>snapshot -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Oct. 7, 2013