- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Zinc time outs too fast

by Sven Van Caekenberghe

Pavel, Igor, On 14 Jul 2011, at 10:06, Sven Van Caekenberghe wrote: > There could still be some deep problem somewhere (you say the default timeout of 30 shows up in stack), but as far as I can see this works. > > I have said this before, ConnectionTimedOut should in 99% of the case be interpreted as ResourceUnavailable, 30 seconds is an eternity for all but a small number of data or processing heavy requests. Does it work now ? Sven

July 15, 2011

Re: [Pharo-project] Hanging connects, exhausted resources, memory leaks, bocked everything ... Unusable!

by Carlo

Hi Guido How did you come to all your conclusions of Pharo if you simply installed and opened up Pharo 1.2.1 and only ran the tests? Memory leaks, connections, unusable etc??? If you have any explicit and constructive feedback then the Pharo community can at least use that to improve it.... Cheers Carlo On 15 Jul 2011, at 12:39 PM, Guido Stepken wrote: I am doing server tuning, building up fast server systems for a very long time now. Yesterday i installed 1.2.1, expecting to see a far more matured Pharo Smalltalk, stable, pretty nice new features. I opened up the Memory Grapher, hmmm.... works fine, watching memory pumping. A bit strange, seeing a Pharo consuming and freeing megabytes of memory space without any load. But ok! Then i opened up TestSuites, marked some tests, let them run. Ups! Desktop hanging. I expected to have with Pharo a well done, stable multitasking environment, but Pharo hangs everywhere, is leaking lots of memory, is keeping up connections, wasting resources unneccessarily, having problems with internal race conditions on semaphores, mutexes, feels same like "Big Kernel Lock", but even without MultiProcessing. The Pharo Team IMHO is very much missing important knowledge about modern Operating System Design, what Pharo Smalltalk OS is in fact, without being able to fulfill the minimum standards i expect from a usable Smalltalk OS. As system operator or enterprise i cannot offer such a system, that has to be restarted twenty times a day, due to hangs, memory leaks, sucking connection handles, ..., whatever! tnx for your understanding! regards, Guido Stepken

July 15, 2011

[Pharo-project] Hanging connects, exhausted resources, memory leaks, bocked everything ... Unusable!

by Guido Stepken

I am doing server tuning, building up fast server systems for a very long time now. Yesterday i installed 1.2.1, expecting to see a far more matured Pharo Smalltalk, stable, pretty nice new features. I opened up the Memory Grapher, hmmm.... works fine, watching memory pumping. A bit strange, seeing a Pharo consuming and freeing megabytes of memory space without any load. But ok! Then i opened up TestSuites, marked some tests, let them run. Ups! Desktop hanging. I expected to have with Pharo a well done, stable multitasking environment, but Pharo hangs everywhere, is leaking lots of memory, is keeping up connections, wasting resources unneccessarily, having problems with internal race conditions on semaphores, mutexes, feels same like "Big Kernel Lock", but even without MultiProcessing. The Pharo Team IMHO is very much missing important knowledge about modern Operating System Design, what Pharo Smalltalk OS is in fact, without being able to fulfill the minimum standards i expect from a usable Smalltalk OS. As system operator or enterprise i cannot offer such a system, that has to be restarted twenty times a day, due to hangs, memory leaks, sucking connection handles, ..., whatever! tnx for your understanding! regards, Guido Stepken

July 15, 2011

Re: [Pharo-project] News about the consortium :)

by Thierry Lebourque

great news! Thank you 2011/7/14 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Hi guys > > just to let you know that INRIA validated our idea to build a consortium. > We are checking the details with them. The discussion will probably continue in September but this is a good news > since they are ready to finance an engineer. Now we have to sort out everything. > > Stef >

July 14, 2011

Re: [Pharo-project] getting notice of text selection

by Tudor Girba

Hi, On 14 Jul 2011, at 16:35, Alain Plantec wrote: > Le 14/07/2011 11:15, Tudor Girba a Ã©crit : >> Hi, >> >> How can I get a notice when the selection changes in a PluggableTextMorph? I see no obvious hook. > AFAIK, no hook in PluggableTextMorph. > > When the selection is changed, an editor sends #storeSelectionInParagraph to itself. maybe one can start from here to add a hook. Great. Thanks. This one worked. So now I have: GLMPluggableTextMorph>>textMorphClass ^ GLMTextMorphForEditView GLMTextMorphForEditView>>editorClass ^ GLMSmalltalkEditor GLMSmalltalkEditor>>storeSelectionInParagraph super storeSelectionInParagraph. self morph ifNotNil: [ self morph editView announceSelectionFrom: self startIndex to: self stopIndex - 1 ] Beautiful. I just hope I won't need to change that in the near future :). Cheers, Doru > There is also TextMorph>>#selectionChanged but it is more for selection drawing purpose. If I remember well, it is also sent when the textmorph is scrolled. > > hope it helps > Cheers > Alain > > >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> >> "Obvious things are difficult to teach." >> >> >> >> >> > > -- www.tudorgirba.com "Every now and then stop and ask yourself if the war you're fighting is the right one."

July 14, 2011

[Pharo-project] About cs...

by StÃ©phane Ducasse

Hi guys I know that MC offers bad properties but it also offers some huge benefits. For example that we can merge and identify conflict quite fast. So please use MC because it makes my work simpler. Stef

July 14, 2011

[Pharo-project] [update 1.4] #14039

by StÃ©phane Ducasse

14039 ----- - Issue 3916: Cannot input some Russian characters at text editors. Thanks guys - Issue 4523: SetElement comment is missing. Thanks Nicolas Cellier

July 14, 2011

[Pharo-project] [update 1.4] #14038

by StÃ©phane Ducasse

14038 ----- - Issue 4413: Better error message for MC. Thanks Camillo Bruni and FBS. - Issue 4507: MC Commit. Thanks Camillo Bruni. I will continue to integrate some fixes regularly now. In my radar: Ring migration FS added to the image RPackage Stef

July 14, 2011

Re: [Pharo-project] News about the consortium :)

by Luc Fabresse

Great Job! Keep pushing ;-) #Luc 2011/7/14 Sven Van Caekenberghe <sven(a)beta9.be> > Super! > > On 14 Jul 2011, at 10:29, StÃ©phane Ducasse wrote: > > > Hi guys > > > > just to let you know that INRIA validated our idea to build a consortium. > > We are checking the details with them. The discussion will probably > continue in September but this is a good news > > since they are ready to finance an engineer. Now we have to sort out > everything. > > > > Stef > > >

July 14, 2011

Re: [Pharo-project] CI down

by Igor Stasenko

yes it seems to be down now. i will check with admins On 14 July 2011 13:33, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > it is different server, for Pharo 1.4 the server > https://ci.lille.inria.fr/pharo/ is used. > > -- Pavel > > On Thu, Jul 14, 2011 at 12:29 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> It works for me. >> https://pharo-ic.lille.inria.fr/hudson/ >> >> Doru >> >> >> On 14 Jul 2011, at 12:26, Pavel Krivanek wrote: >> >>> The server is not accessible however building works. I got e-mail >>> about finished successful build. >>> >>> -- Pavel >>> >>> On Thu, Jul 14, 2011 at 9:40 AM, Pavel Krivanek >>> <pavel.krivanek(a)gmail.com> wrote: >>>> Jenkins server https://ci.lille.inria.fr/pharo/ is not responding. >>>> >>>> -- Pavel >>>> >>> >> >> -- >> www.tudorgirba.com >> >> "Beauty is where we see it." >> >> >> >> >> > > -- Best regards, Igor Stasenko AKA sig.

July 14, 2011