May 2016 - Pharo-users - lists.pharo.org

Having a more robust PharoLauncher in low-bandwidth conditions

by Serge Stinckwich

Dear all, in low-bandwidth countries, this is almost impossible to use PharoLauncher to dl new images from the CI. The problem is not really the speed (you just have to wait) but the robustness of the system. Most of the time, you PharoLauncher crash or you have an error like : "can't find EOCD position" before the end the of the download. I dunno exactly how PharoLauncher download images, but is it possible to think about a more robust way to dl images ? To be able to continue a dl if a network problem occurs (something like wget or curl) ? Thank you. -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

May 25, 2016

Re: [Pharo-users] Lockup when inspecting Text

by Henrik Nergaard

Could you post the string/text object you have trouble inspecting? Both: "Text new inspect" and " (String loremIpsum: 1234) asText inspect" works fine for me (Image 60035). I can't interrupt the display (Ctrl-.). Try (Alt-.) Best regards, Henrik -----Original Message----- From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Alistair Grant Sent: Wednesday, May 25, 2016 5:56 PM To: pharo-users(a)lists.pharo.org Subject: [Pharo-users] Lockup when inspecting Text Hi All, I've got a Text object which I can inspect the string or the runs, but when I attempt to inspect the text object itself Pharo goes into a CPU loop and becomes unresponsive. I can't interrupt the display (Ctrl-.). I've attempted to step through the code to find the problem, however Pharo is going into a CPU loop when returning from GLMMorphicPageRenderer>>render:. I've included the stack trace leading to #render below. At the moment I'm struggling for ideas on how to track this down. Any suggestions? Thanks! Alistair The stack trace just before returning from #render: is: GLMMorphicPagerRenderer>>render: GLMMorphicPagerRenderer class(GLMMorphicWidgetRenderer class)>>render:from: GLMMorphicRenderer>>renderPager: GLMPager>>renderGlamorouslyOn: GLMMorphicRenderer(GLMRenderer)>>render: GLMMorphicTabbedRenderer(GLMMorphicWidgetRenderer)>>renderObject: GLMMorphicTabbedRenderer(GLMMorphicWidgetRenderer)>>renderWithTitleOrNil: GLMMorphicTabbedRenderer>>render: GLMMorphicTabbedRenderer class(GLMMorphicWidgetRenderer class)>>render:from: GLMMorphicRenderer>>renderTabbedCompositePresentation: GLMTabbedArrangement>>renderGlamorouslyOn: GTInspector(GLMCompositePresentation)>>renderGlamorouslyOn: GLMMorphicRenderer(GLMRenderer)>>render: GLMMorphicWindowRenderer(GLMMorphicWidgetRenderer)>>renderObject: GLMMorphicWindowRenderer>>render: GLMMorphicWindowRenderer class(GLMMorphicWidgetRenderer class)>>render:from: GLMMorphicRenderer>>open: GTInspector(GLMCompositePresentation)>>openWith: GTInspector(GLMCompositePresentation)>>openOn:with: GTInspector(GLMCompositePresentation)>>openOn: GTInspector>>openOn: GTInspector class>>openOn: GTInspector class>>inspect: Text(Object)>>inspect ^^^^ This is where I'm attempting to inspect the object. OrderedCollection>>DoIt OpalCompiler>>evaluate RubSmalltalkEditor>>evaluate:andDo: RubSmalltalkEditor>>highlightEvaluateAndDo: [ textMorph textArea editor highlightEvaluateAndDo: ann action. textMorph shoutStyler style: textMorph text ] in [ textMorph textArea handleEdit: [ textMorph textArea editor highlightEvaluateAndDo: ann action. textMorph shoutStyler style: textMorph text ] ] in GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>actOnHighlightAndEvaluate: RubEditingArea(RubAbstractTextArea)>>handleEdit: [ textMorph textArea handleEdit: [ textMorph textArea editor highlightEvaluateAndDo: ann action. textMorph shoutStyler style: textMorph text ] ] in GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>actOnHighlightAndEvaluate: WorldState>>runStepMethodsIn: WorldMorph>>runStepMethods WorldState>>doOneCycleNowFor: WorldState>>doOneCycleFor: WorldMorph>>doOneCycle [ [ World doOneCycle. Processor yield. false ] whileFalse: [ ] ] in MorphicUIManager>>spawnNewProcess [ self value. Processor terminateActive ] in BlockClosure>>newProcess

May 25, 2016

Re: [Pharo-users] Lockup when inspecting Text

by Alistair Grant

On Wed, May 25, 2016 at 05:56:27PM +0200, Alistair Grant wrote: > Hi All, > > I've got a Text object which I can inspect the string or the runs, but > when I attempt to inspect the text object itself Pharo goes into a CPU > loop and becomes unresponsive. I can't interrupt the display (Ctrl-.). > > I've attempted to step through the code to find the problem, however > Pharo is going into a CPU loop when returning > from GLMMorphicPageRenderer>>render:. > > I've included the stack trace leading to #render below. At the moment > I'm struggling for ideas on how to track this down. > > Any suggestions? > > Thanks! > Alistair P.S.: Pharo5.0 Latest update: #50757 OS: 4.5.4-1-ARCH > > > The stack trace just before returning from #render: is: > > GLMMorphicPagerRenderer>>render: > GLMMorphicPagerRenderer class(GLMMorphicWidgetRenderer class)>>render:from: > GLMMorphicRenderer>>renderPager: > GLMPager>>renderGlamorouslyOn: > GLMMorphicRenderer(GLMRenderer)>>render: > GLMMorphicTabbedRenderer(GLMMorphicWidgetRenderer)>>renderObject: > GLMMorphicTabbedRenderer(GLMMorphicWidgetRenderer)>>renderWithTitleOrNil: > GLMMorphicTabbedRenderer>>render: > GLMMorphicTabbedRenderer class(GLMMorphicWidgetRenderer class)>>render:from: > GLMMorphicRenderer>>renderTabbedCompositePresentation: > GLMTabbedArrangement>>renderGlamorouslyOn: > GTInspector(GLMCompositePresentation)>>renderGlamorouslyOn: > GLMMorphicRenderer(GLMRenderer)>>render: > GLMMorphicWindowRenderer(GLMMorphicWidgetRenderer)>>renderObject: > GLMMorphicWindowRenderer>>render: > GLMMorphicWindowRenderer class(GLMMorphicWidgetRenderer > class)>>render:from: > GLMMorphicRenderer>>open: > GTInspector(GLMCompositePresentation)>>openWith: > GTInspector(GLMCompositePresentation)>>openOn:with: > GTInspector(GLMCompositePresentation)>>openOn: > GTInspector>>openOn: > GTInspector class>>openOn: > GTInspector class>>inspect: > Text(Object)>>inspect > > ^^^^ > This is where I'm attempting to inspect the object. > > > OrderedCollection>>DoIt > OpalCompiler>>evaluate > RubSmalltalkEditor>>evaluate:andDo: > RubSmalltalkEditor>>highlightEvaluateAndDo: > [ textMorph textArea editor highlightEvaluateAndDo: ann action. > textMorph shoutStyler style: textMorph text ] in [ textMorph textArea > handleEdit: [ textMorph textArea editor highlightEvaluateAndDo: > ann action. > textMorph shoutStyler style: textMorph text ] ] in > GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>actOnHighlightAndEvaluate: > RubEditingArea(RubAbstractTextArea)>>handleEdit: > [ textMorph textArea > handleEdit: [ textMorph textArea editor highlightEvaluateAndDo: > ann action. > textMorph shoutStyler style: textMorph text ] ] in > GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>actOnHighlightAndEvaluate: > WorldState>>runStepMethodsIn: > WorldMorph>>runStepMethods > WorldState>>doOneCycleNowFor: > WorldState>>doOneCycleFor: > WorldMorph>>doOneCycle > [ [ World doOneCycle. > Processor yield. > false ] whileFalse: [ ] ] in MorphicUIManager>>spawnNewProcess > [ self value. > Processor terminateActive ] in BlockClosure>>newProcess >

May 25, 2016

Lockup when inspecting Text

by Alistair Grant

Hi All, I've got a Text object which I can inspect the string or the runs, but when I attempt to inspect the text object itself Pharo goes into a CPU loop and becomes unresponsive. I can't interrupt the display (Ctrl-.). I've attempted to step through the code to find the problem, however Pharo is going into a CPU loop when returning from GLMMorphicPageRenderer>>render:. I've included the stack trace leading to #render below. At the moment I'm struggling for ideas on how to track this down. Any suggestions? Thanks! Alistair The stack trace just before returning from #render: is: GLMMorphicPagerRenderer>>render: GLMMorphicPagerRenderer class(GLMMorphicWidgetRenderer class)>>render:from: GLMMorphicRenderer>>renderPager: GLMPager>>renderGlamorouslyOn: GLMMorphicRenderer(GLMRenderer)>>render: GLMMorphicTabbedRenderer(GLMMorphicWidgetRenderer)>>renderObject: GLMMorphicTabbedRenderer(GLMMorphicWidgetRenderer)>>renderWithTitleOrNil: GLMMorphicTabbedRenderer>>render: GLMMorphicTabbedRenderer class(GLMMorphicWidgetRenderer class)>>render:from: GLMMorphicRenderer>>renderTabbedCompositePresentation: GLMTabbedArrangement>>renderGlamorouslyOn: GTInspector(GLMCompositePresentation)>>renderGlamorouslyOn: GLMMorphicRenderer(GLMRenderer)>>render: GLMMorphicWindowRenderer(GLMMorphicWidgetRenderer)>>renderObject: GLMMorphicWindowRenderer>>render: GLMMorphicWindowRenderer class(GLMMorphicWidgetRenderer class)>>render:from: GLMMorphicRenderer>>open: GTInspector(GLMCompositePresentation)>>openWith: GTInspector(GLMCompositePresentation)>>openOn:with: GTInspector(GLMCompositePresentation)>>openOn: GTInspector>>openOn: GTInspector class>>openOn: GTInspector class>>inspect: Text(Object)>>inspect ^^^^ This is where I'm attempting to inspect the object. OrderedCollection>>DoIt OpalCompiler>>evaluate RubSmalltalkEditor>>evaluate:andDo: RubSmalltalkEditor>>highlightEvaluateAndDo: [ textMorph textArea editor highlightEvaluateAndDo: ann action. textMorph shoutStyler style: textMorph text ] in [ textMorph textArea handleEdit: [ textMorph textArea editor highlightEvaluateAndDo: ann action. textMorph shoutStyler style: textMorph text ] ] in GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>actOnHighlightAndEvaluate: RubEditingArea(RubAbstractTextArea)>>handleEdit: [ textMorph textArea handleEdit: [ textMorph textArea editor highlightEvaluateAndDo: ann action. textMorph shoutStyler style: textMorph text ] ] in GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>actOnHighlightAndEvaluate: WorldState>>runStepMethodsIn: WorldMorph>>runStepMethods WorldState>>doOneCycleNowFor: WorldState>>doOneCycleFor: WorldMorph>>doOneCycle [ [ World doOneCycle. Processor yield. false ] whileFalse: [ ] ] in MorphicUIManager>>spawnNewProcess [ self value. Processor terminateActive ] in BlockClosure>>newProcess

May 25, 2016

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

by Sabine Manaa

note that it only occurs (hanging image) if you do "VORepository current reset" before. Or have a new Image. 2016-05-25 15:38 GMT+02:00 Sabine Manaa <manaa.sabine(a)gmail.com>: > I have a non-responding image with the original code (with the signal) > > 2016-05-25 15:14 GMT+02:00 Holger Freyther [via Smalltalk] <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=4897348&i=0>>: > >> >> > On 25 May 2016, at 15:42, Esteban Lorenzano <[hidden email] >> <http:///user/SendEmail.jtp?type=node&node=4897346&i=0>> wrote: >> > >> > >> >> Hi, >> >> >> > No I donâtâ¦ in part because is not me who make that code, but also >> because it is expected: after, you have: >> > >> > getCollection: aString >> > ^ [ self addCollection: aString capped: false size: nil max: nil ] >> > on: MongoCollectionAlreadyExists >> > do: [ :err | >> > MongoCollection database: self name: aString ] >> > >> > so the idea is to refine the error to separate >> MongoCollectionAlreadyExists so it can later be catch and handled properly. >> >> when adding capped collection support it seemed like a good idea to fail >> if a collection already exists that might not be capped, but given the >> follow up issues I wonder if I/we should restore the original behavior that >> just ignored all errors? >> >> holger >> >> >> ------------------------------ >> If you reply to this email, your message will be added to the discussion >> below: >> >> http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exist… >> To start a new topic under Pharo Smalltalk Users, email [hidden email] >> <http:///user/SendEmail.jtp?type=node&node=4897348&i=1> >> To unsubscribe from Pharo Smalltalk Users, click here. >> NAML >> <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> >> > > > ------------------------------ > View this message in context: Re: Problem with Mongo on Pharo5 > ("collection already exists") > <http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exist…> > > Sent from the Pharo Smalltalk Users mailing list archive > <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at Nabble.com. >

May 25, 2016

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

by Holger Freyther

> On 25 May 2016, at 15:42, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > No I donâtâ¦ in part because is not me who make that code, but also because it is expected: after, you have: > > getCollection: aString > ^ [ self addCollection: aString capped: false size: nil max: nil ] > on: MongoCollectionAlreadyExists > do: [ :err | > MongoCollection database: self name: aString ] > > so the idea is to refine the error to separate MongoCollectionAlreadyExists so it can later be catch and handled properly. when adding capped collection support it seemed like a good idea to fail if a collection already exists that might not be capped, but given the follow up issues I wonder if I/we should restore the original behavior that just ignored all errors? holger

May 25, 2016

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

by Esteban Lorenzano

> On 25 May 2016, at 15:35, Sabine Manaa <manaa.sabine(a)gmail.com> wrote: > > Hi Esteban, > > can you please have a look again, I think you forgot to remove the signal here > (remove signal in the ifTrue case then it works): No I donâtâ¦ in part because is not me who make that code, but also because it is expected: after, you have: getCollection: aString ^ [ self addCollection: aString capped: false size: nil max: nil ] on: MongoCollectionAlreadyExists do: [ :err | MongoCollection database: self name: aString ] so the idea is to refine the error to separate MongoCollectionAlreadyExists so it can later be catch and handled properly. cheers, Esteban > > addCollection: aString capped: aCapped size: aSize max: aMax > | command | > command := SmallDictionary new. > command at: 'create' put: aString. > aCapped ifTrue: [ > command at: 'capped' put: true. > aSize ifNotNil: [command at: 'size' put: aSize]. > aMax ifNotNil: [command at: 'max' put: aMax]]. > [ self command: command ] > on: MongoCommandError > do: [ :error | > "Tolerate error 48: collection already exists" > error isCollectionAlreadyExists > ==>> ifTrue: [ (MongoCollectionAlreadyExists new collectionName: aString) "signal" ] <<== > ifFalse: [ error signal ] ]. > ^MongoCollection database: self name: aString > > 2016-05-25 12:59 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > problem is not in Pharo 5 but in latest version of MongoTalk (who is loaded with Pharo 5 and apparently not with Pharo 4). > I already submitted a fix for it, but you need to load latest version (still no configuration). > > Esteban > > > On 25 May 2016, at 12:18, Sabine Manaa <manaa.sabine(a)gmail.com <mailto:manaa.sabine@gmail.com>> wrote: > > > > Hi, > > > > Is anyone already running Pharo5 with mongoDB already? > > > > loading my configurationOf in a new pharo5 image results in a problem with > > mongDB. > > loading the same in Pharo4 works fine. > > > > I reduced the problem to the following steps for reproduction: > > 1) start Pharo5 and install VoyageMongo from the ProjectCatalog > > 2) tools-> mongo Browser -> I see that I have connection to my database -ok > > 3) (VOMongoRepository host: 'localhost' database: self databaseName) > > enableSingleton. > > 4) load ONLY my model classes which includes e.g. RKASystemMessage - load > > nothing else > > 5) Then I do RKASystemMessage selectAll (there is ONE system message in the > > mongo database) ==> this results in a non-responding image. > > 6) when debugging into the selectAll, I see, that VoyageMongo tries to add a > > collection (systemMessage), which is already there. > > > > in VOMongoRepositoryResolver>>collectionAt: aClass inDatabase: db > > the collections attribute is empty -> this seems to be the problem > > beause then it tries to do db addCollection: collectionName > > which leads to a "collection already exists" mongo reply > > > > If you have a mongo database running, you should be able to reproduce the > > problem. > > > > Regards > > Sabine > > > > > > > > > > -- > > View this message in context: http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exist… <http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exist…> > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > > >

May 25, 2016

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

by Sabine Manaa

I have a non-responding image with the original code (with the signal) 2016-05-25 15:14 GMT+02:00 Holger Freyther [via Smalltalk] < ml-node+s1294792n4897346h21(a)n4.nabble.com>: > > > On 25 May 2016, at 15:42, Esteban Lorenzano <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=4897346&i=0>> wrote: > > > > > > Hi, > > > > No I donâtâ¦ in part because is not me who make that code, but also > because it is expected: after, you have: > > > > getCollection: aString > > ^ [ self addCollection: aString capped: false size: nil max: nil ] > > on: MongoCollectionAlreadyExists > > do: [ :err | > > MongoCollection database: self name: aString ] > > > > so the idea is to refine the error to separate > MongoCollectionAlreadyExists so it can later be catch and handled properly. > > when adding capped collection support it seemed like a good idea to fail > if a collection already exists that might not be capped, but given the > follow up issues I wonder if I/we should restore the original behavior that > just ignored all errors? > > holger > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exist… > To start a new topic under Pharo Smalltalk Users, email > ml-node+s1294792n1310670h65(a)n4.nabble.com > To unsubscribe from Pharo Smalltalk Users, click here > <http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no…> > . > NAML > <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > -- View this message in context: http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exist… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 25, 2016

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

by Sabine Manaa

Hi Esteban, can you please have a look again, I think you forgot to remove the signal here (remove signal in the ifTrue case then it works): addCollection: aString capped: aCapped size: aSize max: aMax | command | command := SmallDictionary new. command at: 'create' put: aString. aCapped ifTrue: [ command at: 'capped' put: true. aSize ifNotNil: [command at: 'size' put: aSize]. aMax ifNotNil: [command at: 'max' put: aMax]]. [ self command: command ] on: MongoCommandError do: [ :error | "Tolerate error 48: collection already exists" error isCollectionAlreadyExists ==>> ifTrue: [ (MongoCollectionAlreadyExists new collectionName: aString) "signal" ] <<== ifFalse: [ error signal ] ]. ^MongoCollection database: self name: aString 2016-05-25 12:59 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > problem is not in Pharo 5 but in latest version of MongoTalk (who is > loaded with Pharo 5 and apparently not with Pharo 4). > I already submitted a fix for it, but you need to load latest version > (still no configuration). > > Esteban > > > On 25 May 2016, at 12:18, Sabine Manaa <manaa.sabine(a)gmail.com> wrote: > > > > Hi, > > > > Is anyone already running Pharo5 with mongoDB already? > > > > loading my configurationOf in a new pharo5 image results in a problem > with > > mongDB. > > loading the same in Pharo4 works fine. > > > > I reduced the problem to the following steps for reproduction: > > 1) start Pharo5 and install VoyageMongo from the ProjectCatalog > > 2) tools-> mongo Browser -> I see that I have connection to my database > -ok > > 3) (VOMongoRepository host: 'localhost' database: self databaseName) > > enableSingleton. > > 4) load ONLY my model classes which includes e.g. RKASystemMessage - load > > nothing else > > 5) Then I do RKASystemMessage selectAll (there is ONE system message in > the > > mongo database) ==> this results in a non-responding image. > > 6) when debugging into the selectAll, I see, that VoyageMongo tries to > add a > > collection (systemMessage), which is already there. > > > > in VOMongoRepositoryResolver>>collectionAt: aClass inDatabase: db > > the collections attribute is empty -> this seems to be the problem > > beause then it tries to do db addCollection: collectionName > > which leads to a "collection already exists" mongo reply > > > > If you have a mongo database running, you should be able to reproduce the > > problem. > > > > Regards > > Sabine > > > > > > > > > > -- > > View this message in context: > http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exist… > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > > >

May 25, 2016

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

by Esteban Lorenzano

problem is not in Pharo 5 but in latest version of MongoTalk (who is loaded with Pharo 5 and apparently not with Pharo 4). I already submitted a fix for it, but you need to load latest version (still no configuration). Esteban > On 25 May 2016, at 12:18, Sabine Manaa <manaa.sabine(a)gmail.com> wrote: > > Hi, > > Is anyone already running Pharo5 with mongoDB already? > > loading my configurationOf in a new pharo5 image results in a problem with > mongDB. > loading the same in Pharo4 works fine. > > I reduced the problem to the following steps for reproduction: > 1) start Pharo5 and install VoyageMongo from the ProjectCatalog > 2) tools-> mongo Browser -> I see that I have connection to my database -ok > 3) (VOMongoRepository host: 'localhost' database: self databaseName) > enableSingleton. > 4) load ONLY my model classes which includes e.g. RKASystemMessage - load > nothing else > 5) Then I do RKASystemMessage selectAll (there is ONE system message in the > mongo database) ==> this results in a non-responding image. > 6) when debugging into the selectAll, I see, that VoyageMongo tries to add a > collection (systemMessage), which is already there. > > in VOMongoRepositoryResolver>>collectionAt: aClass inDatabase: db > the collections attribute is empty -> this seems to be the problem > beause then it tries to do db addCollection: collectionName > which leads to a "collection already exists" mongo reply > > If you have a mongo database running, you should be able to reproduce the > problem. > > Regards > Sabine > > > > > -- > View this message in context: http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exist… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

May 25, 2016