- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Text fixed Bug? emergency evaluator comes up in 3.0

by Sabine KnÃ¶fel

Hi Ben, ok. I took the newest image from the inria file server (30556) tested, closed it because it was ok. While testing I found a new one. https://pharo.fogbugz.com/f/cases/12111/Date-readFrom-4-2-2013-readStream-p… This is not important for me but I think this is not correct. If the pharo developers do not want to get such "inch picker" (Korinthenkacker) bug entries, plese delete it :-) Regards Sabine On Fri, Nov 8, 2013 at 11:33 AM, btc [via Smalltalk] < ml-node+s1294792n4720231h56(a)n4.nabble.com> wrote: > Sabine KnÃ¶fel wrote: > > Hi Clement, > > I did not fix it, I only got the mail that it was fixed. Ok, I will do > nothing;-) Thanks. > > The ermergency evaluator is in nautilus. OS: Windows. > MessageNot Understood: ToolRegistry>>shortcuts > > Regards > Sabine > > > > Actually, You should have received a mail previous to that one that said > "Resolved ( Fix review needed)" > which I think is the point that the monkey picks it up. But the monkey > only tests it doesn't break anything. It doesn't test that it fixes your > problem. I think its worthwhile that you try the fix yourself, but just > report what find as a standard comment. Do the same with the image that > the fix is integrated into, and then you can close the Case, if someone > hasn't already beat you to it. > > cheers -Ben > > > On Fri, Nov 8, 2013 at 10:51 AM, ClÃ©ment Bera [hidden email] <http://user/SendEmail.jtp?type=node&node=4720231&i=0>wrote: > > > > Hello, > > > *1) I asssume that my task is to test it? If the test would be ok, should > I click on resolve in Fog Buz?* > > So basically when you resolved your bug, you added a slice and put the > status fix review needed. > > Then, the monkey (which is a script) took the latest pharo image, added > your slice and ran all the tests. If all the tests of the image passed with > your new slice (which is the case), the monkey put the status Fix reviewed > by the monkey, that you have now, and this means your fix does not break > any test in the image. If your slice had broken tests, the monkey would > have put back the status to Work needed. > > So you do not have to do anything right now. Someone will have a look to > review your code and put the status to fix to include (but this should not > be you), this reviewing step is sometimes skipped (it is usually skipped > when the fix is minor or obvious). Lastly, an integrator (usually Marcus, > but it could be Esteban or Stef) will integrate it. > > Your fix should be integrated in the next few days if the code review is > ok. > > > > *2) I downloaded Pharo 3.0 but after selecting the Class Date in the > Browser, I get an emergency evaluator, so I can not test it. Perhaps not > yet time totest? Wait? Is the emergency evaluator reason interesting for > you?* > > No clue. I tried and I had no emergency evaluator. By browser you mean > Nautilus right ? > > > > 2013/11/8 Sabine KnÃ¶fel [hidden email] <http://user/SendEmail.jtp?type=node&node=4720231&i=1> > > Hi, > > I got the Fog Buzz message below. > > 2 Questions: > > 1) I asssume that my task is to test it? If the test would be ok, should I > click on resolve in Fog Buz? > 2) I downloaded Pharo 3.0 but after selecting the Class Date in the > Browser, > I get an emergency evaluator, so I can not test it. Perhaps not yet time > to > test? Wait? Is the emergency evaluator reason interesting for you? > > I want to contribute:-) please tell my how :-) > > Regards > Sabine > > ############################## > A FogBugz case was edited by Ulysse The Galactic Monkey From Outer Space. > > Case ID: 11222 > Title: Date readFrom:pattern: (year 2 decimals not 20xx but 00xx) > Status: Resolved (Fix Reviewed by the Monkey) > Category: Bug > Project: Chronology > Area: 1. Pharo Image > Priority: 5 - Fix If Time > Milestone: Pharo3.0: 30/03/2014 > Assigned To: Sabine KnÃ¶fel > > URL: https://pharo.fogbugz.com/f/cases/11222 > > > Changes: > Added tag 'Validated in 30555'. > > > > -- > View this message in context:http://forum.world.st/Text-fixed-Bug-emergency-evaluator-comes-up-in-3-0-tp4720186.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://forum.world.st/Text-fixed-Bug-emergency-evaluator-comes-up-in-3-0-tp… > To unsubscribe from Text fixed Bug? emergency evaluator comes up in 3.0, 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/Text-fixed-Bug-emergency-evaluator-comes-up-in-3-0-tp… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 8, 2013

Re: [Pharo-dev] extracting a pier book into pillar files

by Tudor Girba

Ok. I will try to write the script myself and let you know. Doru On Fri, Nov 8, 2013 at 11:33 AM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > On Thu, Nov 7, 2013 at 4:17 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Should I understand that you are working on this? Any timeline? > > > I'm working on reimplementing a nice visitor for the document model > (because the one of Pier-Book was really hackish). But the Pier-Book > still works fine and you can use that for now. > > I don't have any plan to write a script to do the migration of existing > books. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 8, 2013

Menu enabled not refreshing

by roberto.minelli＠usi.ch

Hi, I think I spotted a bug. When registering a menu item I think the message PragmaMenuAndShortcutRegistration>>#enabled: passing a block is not working correctly. It seems that the enabled state is somewhat cached, i.e., if the block value passes from true to false due to a certain condition in the model, the enabled state is not changed. Are you aware of this? Am I missing something (i.e., force the refresh or something). Thanks in advance, Roby

Nov. 8, 2013

Re: [Pharo-dev] extracting a pier book into pillar files

by Damien Cassou

On Thu, Nov 7, 2013 at 4:17 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Should I understand that you are working on this? Any timeline? I'm working on reimplementing a nice visitor for the document model (because the one of Pier-Book was really hackish). But the Pier-Book still works fine and you can use that for now. I don't have any plan to write a script to do the migration of existing books. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Nov. 8, 2013

Re: [Pharo-dev] Text fixed Bug? emergency evaluator comes up in 3.0

by btc＠openinworld.com

Nov. 8, 2013

Re: [Pharo-dev] Parsing expressions and Opal

by Gisela Decuzzi

Ok, it would be nice to avoid using the parser directly. But we can change it in the future, for now we have a new version for https://pharo.fogbugz.com/f/cases/10983/Represent-a-class-definition-with-A… in inbox. Thanks! 2013/11/8 Marcus Denker <marcus.denker(a)inria.fr> > > On 07 Nov 2013, at 22:14, Gisela Decuzzi <giseladecuzzi(a)gmail.com> wrote: > > > Hello, we were working on the issue 10983 plus smart suggestion, > specially for a class definition. > > In a moment I need to parse a class definition, I treat as the normal > case: > > root := OpalCompiler new > > source: context code; > > useFaultyForParsing: true; > > parse. > > And as a result we obtain a Method Node, browsing the code we saw that > Opal can parse code as an expresion, but instead it is treating the code as > method because of: "self compilationContext noPattern" is false, when we > changed the boolean to true we obtain a return node for the class > definition and everything got messy. > > > > Can someone help us to use Opal in the right way? > > > > The problem is that #noPattern is only used for compiling DoIts, and > those are more than just an expression (return added, access to temps > rewrittenâ¦). > > So for now, the best (yet ugly) thing is to just use RBParser directly, > and we later have to think a bit about the API of the OpalCompiler facade, > especially > considering it is both a facade to just the parser *and* to the compiler, > and e.g expression parsing is very different from parsing a doit, even > though one > would think they are the same. > > So for now, just use the RBParser directly, I would say (there are lots of > direct users of it, we can only remove them in Pharo4 when we have just one > AST). > > Marcus > > >

Nov. 8, 2013

Re: [Pharo-dev] Text fixed Bug? emergency evaluator comes up in 3.0

by Marcus Denker

On 08 Nov 2013, at 11:15, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> wrote: > Hi Clement, > > I did not fix it, I only got the mail that it was fixed. Ok, I will do nothing;-) Thanks. > > The ermergency evaluator is in nautilus. OS: Windows. > MessageNot Understood: ToolRegistry>>shortcuts This was fixed with the update this morning. Marcus

Nov. 8, 2013

Re: [Pharo-dev] Text fixed Bug? emergency evaluator comes up in 3.0

by Sabine KnÃ¶fel

Hi Clement, I did not fix it, I only got the mail that it was fixed. Ok, I will do nothing;-) Thanks. The ermergency evaluator is in nautilus. OS: Windows. MessageNot Understood: ToolRegistry>>shortcuts Regards Sabine On Fri, Nov 8, 2013 at 10:51 AM, ClÃ©ment Bera <bera.clement(a)gmail.com>wrote: > Hello, > > > *1) I asssume that my task is to test it? If the test would be ok, should > I click on resolve in Fog Buz?* > > So basically when you resolved your bug, you added a slice and put the > status fix review needed. > > Then, the monkey (which is a script) took the latest pharo image, added > your slice and ran all the tests. If all the tests of the image passed with > your new slice (which is the case), the monkey put the status Fix reviewed > by the monkey, that you have now, and this means your fix does not break > any test in the image. If your slice had broken tests, the monkey would > have put back the status to Work needed. > > So you do not have to do anything right now. Someone will have a look to > review your code and put the status to fix to include (but this should not > be you), this reviewing step is sometimes skipped (it is usually skipped > when the fix is minor or obvious). Lastly, an integrator (usually Marcus, > but it could be Esteban or Stef) will integrate it. > > Your fix should be integrated in the next few days if the code review is > ok. > > > > *2) I downloaded Pharo 3.0 but after selecting the Class Date in the > Browser, I get an emergency evaluator, so I can not test it. Perhaps not > yet time totest? Wait? Is the emergency evaluator reason interesting for > you?* > > No clue. I tried and I had no emergency evaluator. By browser you mean > Nautilus right ? > > > > 2013/11/8 Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> > >> Hi, >> >> I got the Fog Buzz message below. >> >> 2 Questions: >> >> 1) I asssume that my task is to test it? If the test would be ok, should I >> click on resolve in Fog Buz? >> 2) I downloaded Pharo 3.0 but after selecting the Class Date in the >> Browser, >> I get an emergency evaluator, so I can not test it. Perhaps not yet time >> to >> test? Wait? Is the emergency evaluator reason interesting for you? >> >> I want to contribute:-) please tell my how :-) >> >> Regards >> Sabine >> >> ############################## >> A FogBugz case was edited by Ulysse The Galactic Monkey From Outer Space. >> >> Case ID: 11222 >> Title: Date readFrom:pattern: (year 2 decimals not 20xx but 00xx) >> Status: Resolved (Fix Reviewed by the Monkey) >> Category: Bug >> Project: Chronology >> Area: 1. Pharo Image >> Priority: 5 - Fix If Time >> Milestone: Pharo3.0: 30/03/2014 >> Assigned To: Sabine KnÃ¶fel >> >> URL: https://pharo.fogbugz.com/f/cases/11222 >> >> >> Changes: >> Added tag 'Validated in 30555'. >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Text-fixed-Bug-emergency-evaluator-comes-up-in-3-0-tp… >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> >

Nov. 8, 2013

FogBugz down night Sat->Sun

by Marcus Denker

Hi, The issue tracker will be down Saturday night: "We will be performing maintenance on the storage infrastructure of FogBugz and Kiln On Demand on November 10 at 0300 UTC (November 9, 2200 EST). Both FogBugz and Kiln will be unavailable for four hours."

Nov. 8, 2013

Re: [Pharo-dev] did you noticed the nice fly by help?

by btc＠openinworld.com

StÃ©phane Ducasse wrote: > Guys > > have a look, now we can all know what is Soup, Seaside, Athens, Shout, â¦. ! > Screen Shot 2013-11-07 at 16.14.26.png > > > this is why we should have configurationOf in the image and also why they should > define catalog meta-data. > > Stef > > PS: Hernan you can say to your students that we addressed his concerns! > Very nice. Thanks Stef.

Nov. 8, 2013