- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Bug for harvesting

by Adrian Lienhard

Fix looks ok. Not sure why setting the superclass to nil is actually needed, but else the test is not green (note, the "requires algorithm" was introduced by David Vainsencher and was originally implemented by Nathanael; does somebody use it? maybe in the Squeak-dev image?). Adrian On Jun 11, 2008, at 20:50 , Victor Rodriguez wrote: > On Wed, Jun 11, 2008 at 1:12 PM, Norbert Hartl <norbert(a)hartl.name> > wrote: >> Hi, >> >> I opened a bug a few minutes ago which you may find interesting >> for harvest. >> >> http://bugs.squeak.org/view.php?id=7090 > > I have filed this as Issue 13. I left the state as NEW. > > Saludos, > > Victor. > >> Norbert >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 12, 2008

Re: [Pharo-project] Strange bug in TraitsTest

by Adrian Lienhard

I don't see what could testRootsOfTheWorld be useful for. Anyway, the reason why this fails is because for the traits tests I use test resources and they are set up before all tests are run and testRootsOfTheWorld asserts that there are exactly 3 classes in the system that do not have a superclass. There are two simple solutions for this. Either remove testRootsOfTheWorld or change the test classes created in TraitsRescource to inherit from Object instead of ProtoObject. I would do the former unless somebody has a convincing argument for keeping that test in the image. Adrian NB: I'll also fix #testLocalMethodWithSameCodeInTrait when I'm at it (this tests that there do not exist duplicated methods between a trait and a class using the trait) On Jun 11, 2008, at 19:24 , Norbert Hartl wrote: > If you open a test runner and select only KernelTests-ClassTest and > TraitsTests-TraitsTestCase you may find a failure > > ClassTest>>testRootsOfTheWorld > > But I don't understand fully why it appears. I had once > the chance to get a debugger on the failure (which does > usually not work on this failure) and so I know that the > rootsOfTheWorld (which is usually 3) is 6 in size containing > additionally classes C3 C4 and C6. The ones which are created > by TraitsTestCase (see my last mail "Bug for harvest"). > > They all have a superclass of nil but they aren't included > in the SystemNavigation. (conditions for being included in > the rootsOfTheWorld) > > If you press "Run selected" again the same error occurrs > while pressing "Run failures" gives you all green (ok, it > is this way in my case) > > And I can't reproduce the same in a 3.10 image. > > It seems that there is a timing problem involved. Selecting > only the two test cases I get the failure every time (or nearly). > Selecting all tests it appears only at random. > > Any hints? > > Norbert > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 12, 2008

Re: [Pharo-project] [ANN] New release

by Victor Rodriguez

Replaying to two messages: On Thu, Jun 12, 2008 at 2:47 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > On Wed, 2008-06-11 at 21:22 -0400, Victor Rodriguez wrote: [snip] >> BTW, PharoReady.cs is not available. Stephane, could you please add it? >> > I added it. I've put it into the svn and linked it from there. I don't > think the initial cs has be add inria. > > Norbert On Thu, Jun 12, 2008 at 5:07 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > It is there. > > http://pharo.gforge.inria.fr/PharoReady.cs I would say put the PharoReady.cs on the files section of the INRIA gforge. I would put it right under "Squeak / 3.9.1-7075" so that all the files needed to build Pharo from scratch are together. If we are going to use INRIA gforge for files, lets put *all* the files there, specially "published" files such as this one. If we ever really need to revision something, then we can use the SVN repository. Saludos, Victor Rodriguez. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 12, 2008

Re: [Pharo-project] Trait recent change

by Damien Cassou

On Wed, Jun 11, 2008 at 6:03 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Hi Damien, > > Yes. I recently did a refactoring to reduce the number of traits in the > kernel. That is, most of the traits are flattened down and now are only used > for code reuse between the traits and the classes inheritance branches > (traits count went down from 17 to 6). > > So if your packages change methods in traits that are now gone, you have to > adapt your packages. However, all changes I did are behavior preserving. Thank you -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 12, 2008

Re: [Pharo-project] [ANN] New release

by StÃ©phane Ducasse

It is there. http://pharo.gforge.inria.fr/PharoReady.cs

June 12, 2008

Re: [Pharo-project] Pharo, squeak and the tickets

by StÃ©phane Ducasse

On Jun 12, 2008, at 1:43 AM, Victor Rodriguez wrote: > On Wed, Jun 11, 2008 at 5:49 PM, Norbert Hartl <norbert(a)hartl.name> > wrote: > [snip] >> What would you prefer? >> >> 1. Opening issues where they belong first and let "the others" >> harvest what they think they need? >> 2. Playing back the issues to bugs.squeak.org if we find a bug >> that belongs also to squeak and bring them back by harvesting? > > This is what I propose: > > * If an issue applies to Squeak, file a report on Mantis. > >> How do we want to harvest fixes from other places? >> >> 1. Having a wiki page where issues found are written down? >> 2. Opening tickets on the google tracker for this? This would >> be "to harvest" tickets. > > * File an issue for everything we want to do in Pharo in the google > tracker, *including* for "harvesting" fixes in other projects. Yes I think that having only one flow of fixes is important. > > > Thus, I would still file an issue on the google tracker for Mantis > reports. Such issues should probably follow a template, and have a > label that indicates their origin (in addition to the description). > > As a matter of fact, I think we should file an issue for every fix > listed in the wiki pages in ThreeDotTenFixes, ThreeDotTenDotOneFixes, > etc.. This way, people can assign to themselves a given fix, and we > can more easily keep a handle on things. Yes > > The issue tracker should be the *one* place where you can find what > nees to be done. Yes > > > BTW, this leads to something else I wanted to bring up. Currently, > "harvest" means two things: 1) Put in Pharo a fix available in Squeak > (or Croquet, etc..); and 2) Move a package from the PharoInbox into > the Pharo update stream. Could we come up with a different name for > 2? Something along the lines of 'integrate', 'validate', 'process', > etc.. "Stephane is processing fix X in the PharoInbox". Yes if you have some clearer ideas than me shoot stef > > > Saludos, > > VÃctor RodrÃguez. > > >> Norbert >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 12, 2008

Re: [Pharo-project] Bug for harvesting

by StÃ©phane Ducasse

yes you are right. I will ping samuel for a logo and a nice coloring scheme On Jun 11, 2008, at 11:20 PM, Norbert Hartl wrote: > On Wed, 2008-06-11 at 14:50 -0400, Victor Rodriguez wrote: >> On Wed, Jun 11, 2008 at 1:12 PM, Norbert Hartl <norbert(a)hartl.name> >> wrote: >>> Hi, >>> >>> I opened a bug a few minutes ago which you may find interesting >>> for harvest. >>> >>> http://bugs.squeak.org/view.php?id=7090 >> >> I have filed this as Issue 13. I left the state as NEW. >> > I don't think it is good to open tickets in two different bug > trackers. I opened it on squeak.org because it is a defect that > doesn't belong to pharo. Things get messed quickly this way. > There is a wiki page MantisBugsHarvested. Why shouldn't we have > another page for bugs supposed to be harvested. They exist for > 3.10 already. > > Norbert > > P.S.: I cannot create pages in the wiki. Can someone add me, please! > The account is my email address. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 12, 2008

Re: [Pharo-project] [ANN] New release

by Norbert Hartl

It turns a 3.9.1 image into pharo image which is able to receive the pharo update stream. It's just were everything began :) Norbert On Thu, 2008-06-12 at 10:23 +0200, Serge Stinckwich wrote: > Sorry what is the purpose of this file ? > > 2008/6/12 Norbert Hartl <norbert(a)hartl.name>: > > On Wed, 2008-06-11 at 21:22 -0400, Victor Rodriguez wrote: > >> On Wed, Jun 11, 2008 at 7:54 PM, Victor Rodriguez <victorr(a)gmail.com> wrote: > >> > On Wed, Jun 11, 2008 at 3:51 PM, StÃ©phane Ducasse > >> > <stephane.ducasse(a)inria.fr> wrote: > >> > [snip] > >> >> Is is politically really important that we use the inria infrastructure. > >> >> It will help us building Smalltalk presence inside INRIA. > >> >> So at then end we will not use the forge but only the file because we need > >> >> these counters > >> >> at that place :) > >> > > >> > Fair enough. I have disabled the "Downloads" tab in googlecode. > >> > >> I thought things better and just turned the "Downloads" tab into a > >> wiki page to redirect people to the right place. > >> > >> BTW, PharoReady.cs is not available. Stephane, could you please add it? > >> > > I added it. I've put it into the svn and linked it from there. I don't > > think the initial cs has be add inria. > > > > Norbert > > > >> Thanks, > >> > >> Victor. > >> > >> > >> > VÃctor. > >> > > >> >>> I will volunteer again and move all the existing files over. (As a > >> >>> matter of fact, I had been thinking of moving the files then proposing > >> >>> the change, but I just haven't had a chance to do it.) > >> >> > >> >> Please don't there are issues more complex under the surface but this is not > >> >> linked with pharo by itself. > >> >> > >> >>> > >> >>> > >> >>> Victor. > >> >>> > >> >>> > >> >>>> On Jun 11, 2008, at 1:39 PM, Oscar Nierstrasz wrote: > >> >>>> > >> >>>>> > >> >>>>> Ah, I thought it *was* a pharo-dev image -- it was listed under > >> >>>>> "pharo-dev" on the downloads page. > >> >>>>> > >> >>>>> http://gforge.inria.fr/frs/?group_id=1299 > >> >>>>> > >> >>>>> - on > >> >>>>> > >> >>>>> On Jun 11, 2008, at 11:12, Damien Cassou wrote: > >> >>>>> > >> >>>>>> On Wed, Jun 11, 2008 at 9:56 AM, Oscar Nierstrasz <oscar(a)iam.unibe.ch> > >> >>>>>> wrote: > >> >>>>>>> > >> >>>>>>> Great! > >> >>>>>>> > >> >>>>>>> Just noticed two things: > >> >>>>>>> > >> >>>>>>> - Test Runner is missing from the Tools flap -- shouldn't it be there? > >> >>>>>> > >> >>>>>> > >> >>>>>> I think Pharo should not care about such things. Just use pharo-dev if > >> >>>>>> you want a prepared pharo image for developers. > >> >>>>>> > >> >>>>>> -- > >> >>>>>> Damien Cassou > >> >>>>>> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > >> >>>>>> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > >> >>>>>> > >> >>>>>> _______________________________________________ > >> >>>>>> Pharo-project mailing list > >> >>>>>> Pharo-project(a)lists.gforge.inria.fr > >> >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> >>>>>> > >> >>>>> > >> >>>>> > >> >>>>> _______________________________________________ > >> >>>>> Pharo-project mailing list > >> >>>>> Pharo-project(a)lists.gforge.inria.fr > >> >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> >>>>> > >> >>>> > >> >>>> > >> >>>> _______________________________________________ > >> >>>> Pharo-project mailing list > >> >>>> Pharo-project(a)lists.gforge.inria.fr > >> >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> >>>> > >> >>> > >> >>> _______________________________________________ > >> >>> Pharo-project mailing list > >> >>> Pharo-project(a)lists.gforge.inria.fr > >> >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> >>> > >> >> > >> >> > >> >> _______________________________________________ > >> >> Pharo-project mailing list > >> >> Pharo-project(a)lists.gforge.inria.fr > >> >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> >> > >> > > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > Serge Stinckwich > Smalltalkers do: [:it | All with: Class, (And love: it)] > http://blog.doesnotunderstand.org/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 12, 2008

Re: [Pharo-project] [ANN] New release

by Serge Stinckwich

Sorry what is the purpose of this file ? 2008/6/12 Norbert Hartl <norbert(a)hartl.name>: > On Wed, 2008-06-11 at 21:22 -0400, Victor Rodriguez wrote: >> On Wed, Jun 11, 2008 at 7:54 PM, Victor Rodriguez <victorr(a)gmail.com> wrote: >> > On Wed, Jun 11, 2008 at 3:51 PM, StÃ©phane Ducasse >> > <stephane.ducasse(a)inria.fr> wrote: >> > [snip] >> >> Is is politically really important that we use the inria infrastructure. >> >> It will help us building Smalltalk presence inside INRIA. >> >> So at then end we will not use the forge but only the file because we need >> >> these counters >> >> at that place :) >> > >> > Fair enough. I have disabled the "Downloads" tab in googlecode. >> >> I thought things better and just turned the "Downloads" tab into a >> wiki page to redirect people to the right place. >> >> BTW, PharoReady.cs is not available. Stephane, could you please add it? >> > I added it. I've put it into the svn and linked it from there. I don't > think the initial cs has be add inria. > > Norbert > >> Thanks, >> >> Victor. >> >> >> > VÃctor. >> > >> >>> I will volunteer again and move all the existing files over. (As a >> >>> matter of fact, I had been thinking of moving the files then proposing >> >>> the change, but I just haven't had a chance to do it.) >> >> >> >> Please don't there are issues more complex under the surface but this is not >> >> linked with pharo by itself. >> >> >> >>> >> >>> >> >>> Victor. >> >>> >> >>> >> >>>> On Jun 11, 2008, at 1:39 PM, Oscar Nierstrasz wrote: >> >>>> >> >>>>> >> >>>>> Ah, I thought it *was* a pharo-dev image -- it was listed under >> >>>>> "pharo-dev" on the downloads page. >> >>>>> >> >>>>> http://gforge.inria.fr/frs/?group_id=1299 >> >>>>> >> >>>>> - on >> >>>>> >> >>>>> On Jun 11, 2008, at 11:12, Damien Cassou wrote: >> >>>>> >> >>>>>> On Wed, Jun 11, 2008 at 9:56 AM, Oscar Nierstrasz <oscar(a)iam.unibe.ch> >> >>>>>> wrote: >> >>>>>>> >> >>>>>>> Great! >> >>>>>>> >> >>>>>>> Just noticed two things: >> >>>>>>> >> >>>>>>> - Test Runner is missing from the Tools flap -- shouldn't it be there? >> >>>>>> >> >>>>>> >> >>>>>> I think Pharo should not care about such things. Just use pharo-dev if >> >>>>>> you want a prepared pharo image for developers. >> >>>>>> >> >>>>>> -- >> >>>>>> Damien Cassou >> >>>>>> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good >> >>>>>> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) >> >>>>>> >> >>>>>> _______________________________________________ >> >>>>>> Pharo-project mailing list >> >>>>>> Pharo-project(a)lists.gforge.inria.fr >> >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >>>>>> >> >>>>> >> >>>>> >> >>>>> _______________________________________________ >> >>>>> Pharo-project mailing list >> >>>>> Pharo-project(a)lists.gforge.inria.fr >> >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >>>>> >> >>>> >> >>>> >> >>>> _______________________________________________ >> >>>> Pharo-project mailing list >> >>>> Pharo-project(a)lists.gforge.inria.fr >> >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >>>> >> >>> >> >>> _______________________________________________ >> >>> Pharo-project mailing list >> >>> Pharo-project(a)lists.gforge.inria.fr >> >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >>> >> >> >> >> >> >> _______________________________________________ >> >> Pharo-project mailing list >> >> Pharo-project(a)lists.gforge.inria.fr >> >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> > >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/

June 12, 2008

Re: [Pharo-project] Pharo, squeak and the tickets

by Serge Stinckwich

2008/6/12 Victor Rodriguez <victorr(a)gmail.com>: > On Wed, Jun 11, 2008 at 5:49 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > [snip] >> What would you prefer? >> >> 1. Opening issues where they belong first and let "the others" >> harvest what they think they need? >> 2. Playing back the issues to bugs.squeak.org if we find a bug >> that belongs also to squeak and bring them back by harvesting? > > This is what I propose: > > * If an issue applies to Squeak, file a report on Mantis. Yes we could be nice with Squeak ;-) >> How do we want to harvest fixes from other places? >> >> 1. Having a wiki page where issues found are written down? >> 2. Opening tickets on the google tracker for this? This would >> be "to harvest" tickets. > > * File an issue for everything we want to do in Pharo in the google > tracker, *including* for "harvesting" fixes in other projects. > > Thus, I would still file an issue on the google tracker for Mantis > reports. Such issues should probably follow a template, and have a > label that indicates their origin (in addition to the description). > > As a matter of fact, I think we should file an issue for every fix > listed in the wiki pages in ThreeDotTenFixes, ThreeDotTenDotOneFixes, > etc.. This way, people can assign to themselves a given fix, and we > can more easily keep a handle on things. > > The issue tracker should be the *one* place where you can find what > nees to be done. I agree with this plan. > BTW, this leads to something else I wanted to bring up. Currently, > "harvest" means two things: 1) Put in Pharo a fix available in Squeak > (or Croquet, etc..); and 2) Move a package from the PharoInbox into > the Pharo update stream. Could we come up with a different name for > 2? Something along the lines of 'integrate', 'validate', 'process', > etc.. "Stephane is processing fix X in the PharoInbox". > Yes and after the vocabulary is fixed, can we document this vocabulary and the harvesting process in the Wiki. I think we need something like a workflow. -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/

June 12, 2008