January 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Zinc timeouts

by Sven Van Caekenberghe

On 14 Jan 2013, at 22:07, Camillo Bruni <camillobruni(a)gmail.com> wrote: > On 2013-01-14, at 22:05, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> On 14 Jan 2013, at 21:54, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >>>> Issue with slice: http://code.google.com/p/pharo/issues/detail?id=7255 >>>> >>>> Yes, any DNS failure resulted in strange exception handling, IMO. This could indeed improve a couple more bogus situations. >>> >>> thanks >>> >>>> The following should work after you load the slice: >>>> >>>> ZnClient new >>>> timeout: 5; >>>> url: 'http://an.url.that.does.not.exists.ch/foo'; >>>> logToTranscript; >>>> downloadTo: FileSystem workingDirectory. >>> >>> I just tried, seems like your slice improves your example, though I still get issues when changing the number of retries: >>> >>> ZnClient new >>> numberOfRetries: 1; "0 works..." >>> timeout: 5; >>> url: 'http://an.url.that.does.not.exists.ch/foo'; >>> logToTranscript; >>> downloadTo: FileSystem workingDirectory. >>> >>> looks like it is still somewhere in the net resolver... strange >> >> Well, I must admit that I don't really understand why/where it hangs ;-) >> I saw there was a problem with NameLookupFailure and I fixed what I thought was wrong. >> >> Retry happens when something goes wrong, i.e. some exception is thrown. >> It shouldn't make any difference what actually happened. >> >> But testing retry behaviour is hard, I will think about a way to do that in a unit test. > > I can imagine :/, I will try to step through a bit further to get close to the problem. With Camillo's fix for NetNameResolver's ResolverMutex retrying NameLookupFailires now seems to work. Sven

Jan. 15, 2013

Re: [Pharo-project] [squeak-dev] In Memory of Andreas Raab

by StÃ©phane Ducasse

Hi Janko Indeed this is a **really** sad news. We just learned his death now. I was not in sync with andreas' vision but he was a nice and creative opponent. This reminds us that life is short and fragile. Sudden death is always difficult to handle and I wish a lot of strength to his family and friends. I got some family deaths over the years and this is always a difficult moment. Stef > This news are really shock for me. Shock because we lost one of the > brightest Smalltalkers who contributed to our community a lot. > > Janko > > Dne 15. 01. 2013 03:30, piÅ¡e Ron Teitelbaum: >> All, >> >> I met Andreas many years ago. I knew very quickly that Andreas was >> extremely bright and a very interesting person to know. The more I >> found out about him the more we interacted the more I grew to respect >> him and his talent. I was lucky enough to get a chance to work with >> Andreas. Andreas was a phenomenon. The work that he created was >> beautiful. His method precise, his solutions well thought out and he >> was able to create with unmatched dexterity and efficiency. We became >> good friends. I was also lucky enough to be meet Andreas in person for >> the first time at his wedding. Andreas was a very happy man. Kathleen >> was Andreasâ perfect match. >> >> We will miss Andreas terribly not only for his talent, but for how he >> touched our lives. We lost a great friend. The world feels like a much >> smaller place today. Our hearts go out to Kathleen, and to the big >> group of family and friends that loved him so. >> >> Ron Teitelbaum >> >> From Alan Kay: >> >> Dear All >> >> At lunch today we -- Bert, Aran, Yoshiki and myself -- first got word >> (via a phone call from Rita to Bert) that Andreas was suddenly in a >> hospital in serious condition. Then a few minutes later we were told >> that he had died. >> >> At this point we have no other information except that he left normally >> for work this morning. >> >> Bert will let us know when we have more news. >> >> We all loved Andreas and nothing can lesson our grief at this sudden tragedy >> >> Best wishes to all >> >> Alan >> >> >> >> > > -- > Janko MivÅ¡ek > Aida/Web > Smalltalk Web Application Server > http://www.aidaweb.si >

Jan. 15, 2013

Re: [Pharo-project] [Lsehub-staff] SmalltalkHub is back online!

by StÃ©phane Ducasse

thanks Nicolas! Yes doing is always more difficult than the rest :) Stef On Jan 15, 2013, at 1:01 AM, Nicolas Petton wrote: > > After a rather painful debugging/db-restoring session, SmalltalkHub is > back online! > > So...what happened? > > Well, the db got currupted due to a concurrency issue, which is now fixed [1], > resulting in very unstable behavior. Fixing the issue and restoring the > db got SmalltalkHub back on track. > > Did I lose any data? > > Nope. > > What's next? > > I'll keep a close eye on the DB for the coming days and make sure it > runs smoothly. > > Cheers, > Nico > > > [1] http://smalltalkhub.com/#!/~NicolasPetton/SmalltalkHub/diff/Hub-NicolasPett… >

Jan. 15, 2013

Re: [Pharo-project] PasswordHashingFFI package - users should update

by StÃ©phane Ducasse

ok so constant time to answer is better. Stef On Jan 15, 2013, at 9:16 AM, Henrik Sperre Johansen wrote: > On 14.01.2013 22:38, StÃ©phane Ducasse wrote: >> Thanks for sending us this link. It is quite interesting. >> >> Did the people think about using random generated number to change the response time? > Network latency, processor scheduling etc. already add a measure of randomness to the returned values, so the attack already presumes you are able to induce the actual signal from noisy results. > Adding another random factor doesn't really change that, it just means one would have to adjust how the actual signal is extracted. > > Cheers, > Henry >

Jan. 15, 2013

Re: [Pharo-project] Fwd: Problem installing Neptuno

by Esteban Lorenzano

Hi Frank, the problem is that Pharo is a community effort, and there are so much projects around that we cannot track down all the packages (but we are working on a "validator" for metacello to ensure the packages at least load). Eventually, that provokes some incompatibilities... but if you think is just because we are disordered, take a look of what happens in other communities (python, ruby, java, all of them I know have similar problems with their products). I understand your frustration, and we are trying to improve a lot, but a correct publishing mechanism will take some time and effort to come. In the mean time, I just can ask for your understanding and collaboration. Pharo 2.0, btw, will allow shadow variables (same name of variables in different classes, in same hierarchy, or same variable name between an instance variable and a method variable), a decision that also has some consequences, but that will allow this kind of conflicts to load without problems (to actually run, that's another story :) cheers, Esteban On Jan 15, 2013, at 4:01 AM, Frank Church <vfclists(a)gmail.com> wrote: > Is it okay for me to say that something isn't right here? > > The way I see it if something in Neptuno ie GLMTreeMorphModel is going > to be in conflict with MorphTreeModel, then it shouldn't even released > in the first place or clearly marked as a work in progress. > MorphTreeModel appoears to be quite high up the Smalltalk environment > hierarchy. Unless the change which caused the conflict was caused by > introducing a method in MorphTreeModel "after" it was developed in > Glamour which doesn't appear to the case. > > Which raises a few questions: > > 1. When a new version of Pharo is released, is there a set of > packages with specified versions which are supposed to work perfectly > with that Pharo release? > > 2. When a packaged is created is the creator required to list the > exact base release and the combination of packages it is tested > against, eg Pharo 1.4-14557? > > I am not saying this with regards to Neptuno in particular because the > conflict seems to come from Glamour, there is also another "announcer" > method in DBXBrowser but it appears the one in GLMTreeMorphModel is > the culprit. After trying what I can truthfully describe as an > amateurish attempt to refactor the "announcer" method even the Finder > is broken. Basically I changed "announcer" to "announcerGLM" and the > Finder breaks with MNU:False>>announce and I can't revert it. > > It doesn't feel right to me that search an important element in the > IDE should be broken by something lower down the hierarchy. I will try > it on earlier versions of Pharo to see. > > On starting with Pharo I have had to switch among different versions > to get the demos working properly, but this name(space) clash is > simply too jarring > On 14 January 2013 19:46, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> yes, but that means it is present twice in the hierarchy, after loading you can check when it corresponds actually and re-add announcer in MorphTreeModel, rename the one in Neptuno... and commit the fix for Neptuno to the repository... is all community work so feel free to do it :) >> >> Esteban >> >> On Jan 14, 2013, at 8:39 PM, Frank Church <vfclists(a)gmail.com> wrote: >> >>> If "announcer" is removed from MorphTreeModel isn't that likely to >>> break something else that depends on "announcer" being present in >>> MorphTreeModel? >>> >>> Is "announcer" something new in MorphTreeModel and is Neptuno >>> duplicating the function or is it the other round? MorphTreeModel >>> seems to be the UI object and it doesn't feel right to me that a >>> database oriented tool should override something in a UI object. I >>> think if the functionality is duplicated it may be better to rename >>> the "announcer" in Neptuno. >>> >>> >>> On 14 January 2013 16:00, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> that's because somethings on morphic were added for 1.4 summer. >>>> Try removing "announcer" on MorphTreeModel, then load. >>>> >>>> >>>> On Jan 14, 2013, at 4:46 PM, Frank Church <vfclists(a)gmail.com> wrote: >>>> >>>>> Has anyone managed to get Neptuno - ConfigurationOfDBXTools in Pharo 1.4?. >>>>> >>>>> When I try to install Neptuno in Pharo 1.4 I get the error - >>>>> 'announcer is already defined in MorphTreeModel' >>>>> >>>>> ---------- Forwarded message ---------- >>>>> From: Frank Church <vfclists(a)gmail.com> >>>>> Date: 14 January 2013 01:05 >>>>> Subject: Problem installing Neptuno >>>>> To: A friendly place where any question about pharo is welcome >>>>> <pharo-users(a)lists.gforge.inria.fr> >>>>> >>>>> >>>>> When I try to install Neptuno in Pharo 1.4 I get the error - >>>>> 'announcer is already defined in MorphTreeModel' >>>>> >>>>> Gofer it >>>>> squeaksource: 'MetacelloRepository'; >>>>> package: 'ConfigurationOfDBXTools'; >>>>> load. >>>>> >>>>> (((Smalltalk at: #ConfigurationOfDBXTools) >>>>> perform: #project) >>>>> perform: #version: with: #stable) >>>>> load: 'Phoseydon'. >>>>> >>>>> Gofer it >>>>> squeaksource: 'MetacelloRepository'; >>>>> package: 'ConfigurationOfDBXBrowser'; >>>>> load. >>>>> >>>>> (((Smalltalk at: #ConfigurationOfDBXTools) >>>>> perform: #project) >>>>> perform: #version: with: #stable) >>>>> load: 'Neptuno' . >>>>> >>>>> The error happens at the last stage when I am installing Neptuno. >>>>> >>>>> The issue appears in the DBXTalk mailing list - >>>>> http://forum.world.st/Re-Pharo-project-How-to-load-Phoseydon-and-Neptuno-td… >>>>> >>>>> -- >>>>> Frank Church > > > -- > Frank Church > > ======================= > http://devblog.brahmancreations.com >

Jan. 15, 2013

Re: [Pharo-project] PasswordHashingFFI package - users should update

by Henrik Sperre Johansen

On 14.01.2013 22:38, StÃ©phane Ducasse wrote: > Thanks for sending us this link. It is quite interesting. > > Did the people think about using random generated number to change the response time? Network latency, processor scheduling etc. already add a measure of randomness to the returned values, so the attack already presumes you are able to induce the actual signal from noisy results. Adding another random factor doesn't really change that, it just means one would have to adjust how the actual signal is extracted. Cheers, Henry

Jan. 15, 2013

Re: [Pharo-project] Fwd: Problem installing Neptuno

by Tudor Girba

Hi Frank, GLMTreeMorphModel does not have announcer since a long time. You should probably update your code. Furthermore, the latest version of Glamour is made to work with Pharo 1.4. Cheers, Doru On Tue, Jan 15, 2013 at 4:01 AM, Frank Church <vfclists(a)gmail.com> wrote: > Is it okay for me to say that something isn't right here? > > The way I see it if something in Neptuno ie GLMTreeMorphModel is going > to be in conflict with MorphTreeModel, then it shouldn't even released > in the first place or clearly marked as a work in progress. > MorphTreeModel appoears to be quite high up the Smalltalk environment > hierarchy. Unless the change which caused the conflict was caused by > introducing a method in MorphTreeModel "after" it was developed in > Glamour which doesn't appear to the case. > > Which raises a few questions: > > 1. When a new version of Pharo is released, is there a set of > packages with specified versions which are supposed to work perfectly > with that Pharo release? > > 2. When a packaged is created is the creator required to list the > exact base release and the combination of packages it is tested > against, eg Pharo 1.4-14557? > > I am not saying this with regards to Neptuno in particular because the > conflict seems to come from Glamour, there is also another "announcer" > method in DBXBrowser but it appears the one in GLMTreeMorphModel is > the culprit. After trying what I can truthfully describe as an > amateurish attempt to refactor the "announcer" method even the Finder > is broken. Basically I changed "announcer" to "announcerGLM" and the > Finder breaks with MNU:False>>announce and I can't revert it. > > It doesn't feel right to me that search an important element in the > IDE should be broken by something lower down the hierarchy. I will try > it on earlier versions of Pharo to see. > > On starting with Pharo I have had to switch among different versions > to get the demos working properly, but this name(space) clash is > simply too jarring > On 14 January 2013 19:46, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > yes, but that means it is present twice in the hierarchy, after loading > you can check when it corresponds actually and re-add announcer in > MorphTreeModel, rename the one in Neptuno... and commit the fix for Neptuno > to the repository... is all community work so feel free to do it :) > > > > Esteban > > > > On Jan 14, 2013, at 8:39 PM, Frank Church <vfclists(a)gmail.com> wrote: > > > >> If "announcer" is removed from MorphTreeModel isn't that likely to > >> break something else that depends on "announcer" being present in > >> MorphTreeModel? > >> > >> Is "announcer" something new in MorphTreeModel and is Neptuno > >> duplicating the function or is it the other round? MorphTreeModel > >> seems to be the UI object and it doesn't feel right to me that a > >> database oriented tool should override something in a UI object. I > >> think if the functionality is duplicated it may be better to rename > >> the "announcer" in Neptuno. > >> > >> > >> On 14 January 2013 16:00, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >>> that's because somethings on morphic were added for 1.4 summer. > >>> Try removing "announcer" on MorphTreeModel, then load. > >>> > >>> > >>> On Jan 14, 2013, at 4:46 PM, Frank Church <vfclists(a)gmail.com> wrote: > >>> > >>>> Has anyone managed to get Neptuno - ConfigurationOfDBXTools in Pharo > 1.4?. > >>>> > >>>> When I try to install Neptuno in Pharo 1.4 I get the error - > >>>> 'announcer is already defined in MorphTreeModel' > >>>> > >>>> ---------- Forwarded message ---------- > >>>> From: Frank Church <vfclists(a)gmail.com> > >>>> Date: 14 January 2013 01:05 > >>>> Subject: Problem installing Neptuno > >>>> To: A friendly place where any question about pharo is welcome > >>>> <pharo-users(a)lists.gforge.inria.fr> > >>>> > >>>> > >>>> When I try to install Neptuno in Pharo 1.4 I get the error - > >>>> 'announcer is already defined in MorphTreeModel' > >>>> > >>>> Gofer it > >>>> squeaksource: 'MetacelloRepository'; > >>>> package: 'ConfigurationOfDBXTools'; > >>>> load. > >>>> > >>>> (((Smalltalk at: #ConfigurationOfDBXTools) > >>>> perform: #project) > >>>> perform: #version: with: #stable) > >>>> load: 'Phoseydon'. > >>>> > >>>> Gofer it > >>>> squeaksource: 'MetacelloRepository'; > >>>> package: 'ConfigurationOfDBXBrowser'; > >>>> load. > >>>> > >>>> (((Smalltalk at: #ConfigurationOfDBXTools) > >>>> perform: #project) > >>>> perform: #version: with: #stable) > >>>> load: 'Neptuno' . > >>>> > >>>> The error happens at the last stage when I am installing Neptuno. > >>>> > >>>> The issue appears in the DBXTalk mailing list - > >>>> > http://forum.world.st/Re-Pharo-project-How-to-load-Phoseydon-and-Neptuno-td… > >>>> > >>>> -- > >>>> Frank Church > > > -- > Frank Church > > ======================= > http://devblog.brahmancreations.com > > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 15, 2013

Re: [Pharo-project] [squeak-dev] In Memory of Andreas Raab

by Janko MivÅ¡ek

This news are really shock for me. Shock because we lost one of the brightest Smalltalkers who contributed to our community a lot. Janko Dne 15. 01. 2013 03:30, piÅ¡e Ron Teitelbaum: > All, > > I met Andreas many years ago. I knew very quickly that Andreas was > extremely bright and a very interesting person to know. The more I > found out about him the more we interacted the more I grew to respect > him and his talent. I was lucky enough to get a chance to work with > Andreas. Andreas was a phenomenon. The work that he created was > beautiful. His method precise, his solutions well thought out and he > was able to create with unmatched dexterity and efficiency. We became > good friends. I was also lucky enough to be meet Andreas in person for > the first time at his wedding. Andreas was a very happy man. Kathleen > was Andreasâ perfect match. > > We will miss Andreas terribly not only for his talent, but for how he > touched our lives. We lost a great friend. The world feels like a much > smaller place today. Our hearts go out to Kathleen, and to the big > group of family and friends that loved him so. > > Ron Teitelbaum > > From Alan Kay: > > Dear All > > At lunch today we -- Bert, Aran, Yoshiki and myself -- first got word > (via a phone call from Rita to Bert) that Andreas was suddenly in a > hospital in serious condition. Then a few minutes later we were told > that he had died. > > At this point we have no other information except that he left normally > for work this morning. > > Bert will let us know when we have more news. > > We all loved Andreas and nothing can lesson our grief at this sudden tragedy > > Best wishes to all > > Alan > > > > -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

Jan. 15, 2013

Re: [Pharo-project] SmalltalkHub is back online!

by GÃ¶ran Krampe

On 01/15/2013 01:01 AM, Nicolas Petton wrote: > After a rather painful debugging/db-restoring session, SmalltalkHub is > back online! > > So...what happened? > > Well, the db got currupted due to a concurrency issue, which is now fixed [1], > resulting in very unstable behavior. Fixing the issue and restoring the > db got SmalltalkHub back on track. > > Did I lose any data? > > Nope. Great work Nicolas, I know how stressful such situations can be :) regards, GÃ¶ran

Jan. 15, 2013

Re: [Pharo-project] Fwd: Problem installing Neptuno

by Frank Church

Is it okay for me to say that something isn't right here? The way I see it if something in Neptuno ie GLMTreeMorphModel is going to be in conflict with MorphTreeModel, then it shouldn't even released in the first place or clearly marked as a work in progress. MorphTreeModel appoears to be quite high up the Smalltalk environment hierarchy. Unless the change which caused the conflict was caused by introducing a method in MorphTreeModel "after" it was developed in Glamour which doesn't appear to the case. Which raises a few questions: 1. When a new version of Pharo is released, is there a set of packages with specified versions which are supposed to work perfectly with that Pharo release? 2. When a packaged is created is the creator required to list the exact base release and the combination of packages it is tested against, eg Pharo 1.4-14557? I am not saying this with regards to Neptuno in particular because the conflict seems to come from Glamour, there is also another "announcer" method in DBXBrowser but it appears the one in GLMTreeMorphModel is the culprit. After trying what I can truthfully describe as an amateurish attempt to refactor the "announcer" method even the Finder is broken. Basically I changed "announcer" to "announcerGLM" and the Finder breaks with MNU:False>>announce and I can't revert it. It doesn't feel right to me that search an important element in the IDE should be broken by something lower down the hierarchy. I will try it on earlier versions of Pharo to see. On starting with Pharo I have had to switch among different versions to get the demos working properly, but this name(space) clash is simply too jarring On 14 January 2013 19:46, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > yes, but that means it is present twice in the hierarchy, after loading you can check when it corresponds actually and re-add announcer in MorphTreeModel, rename the one in Neptuno... and commit the fix for Neptuno to the repository... is all community work so feel free to do it :) > > Esteban > > On Jan 14, 2013, at 8:39 PM, Frank Church <vfclists(a)gmail.com> wrote: > >> If "announcer" is removed from MorphTreeModel isn't that likely to >> break something else that depends on "announcer" being present in >> MorphTreeModel? >> >> Is "announcer" something new in MorphTreeModel and is Neptuno >> duplicating the function or is it the other round? MorphTreeModel >> seems to be the UI object and it doesn't feel right to me that a >> database oriented tool should override something in a UI object. I >> think if the functionality is duplicated it may be better to rename >> the "announcer" in Neptuno. >> >> >> On 14 January 2013 16:00, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> that's because somethings on morphic were added for 1.4 summer. >>> Try removing "announcer" on MorphTreeModel, then load. >>> >>> >>> On Jan 14, 2013, at 4:46 PM, Frank Church <vfclists(a)gmail.com> wrote: >>> >>>> Has anyone managed to get Neptuno - ConfigurationOfDBXTools in Pharo 1.4?. >>>> >>>> When I try to install Neptuno in Pharo 1.4 I get the error - >>>> 'announcer is already defined in MorphTreeModel' >>>> >>>> ---------- Forwarded message ---------- >>>> From: Frank Church <vfclists(a)gmail.com> >>>> Date: 14 January 2013 01:05 >>>> Subject: Problem installing Neptuno >>>> To: A friendly place where any question about pharo is welcome >>>> <pharo-users(a)lists.gforge.inria.fr> >>>> >>>> >>>> When I try to install Neptuno in Pharo 1.4 I get the error - >>>> 'announcer is already defined in MorphTreeModel' >>>> >>>> Gofer it >>>> squeaksource: 'MetacelloRepository'; >>>> package: 'ConfigurationOfDBXTools'; >>>> load. >>>> >>>> (((Smalltalk at: #ConfigurationOfDBXTools) >>>> perform: #project) >>>> perform: #version: with: #stable) >>>> load: 'Phoseydon'. >>>> >>>> Gofer it >>>> squeaksource: 'MetacelloRepository'; >>>> package: 'ConfigurationOfDBXBrowser'; >>>> load. >>>> >>>> (((Smalltalk at: #ConfigurationOfDBXTools) >>>> perform: #project) >>>> perform: #version: with: #stable) >>>> load: 'Neptuno' . >>>> >>>> The error happens at the last stage when I am installing Neptuno. >>>> >>>> The issue appears in the DBXTalk mailing list - >>>> http://forum.world.st/Re-Pharo-project-How-to-load-Phoseydon-and-Neptuno-td… >>>> >>>> -- >>>> Frank Church -- Frank Church ======================= http://devblog.brahmancreations.com

Jan. 15, 2013