On Oct 22, 2013 4:01 PM, "Goubier Thierry" <thierry.goubier@cea.fr> wrote:
>
>
>
> Le 22/10/2013 15:55, Bruni camillo a ��crit :
>
>> This is exactly the reason I started exporting everything to git and
>> archiving all the images in an accessible way :-P.
>
>
> It certainly was very helpfull and I'll use it again sooner or later.
>
> Would you happen to have a get.pharo.org way of getting a given image number?

Not yet, that is something we have to add.

>> it would be definitely nice to have this more automated.
>
>
>
>
>> On Oct 22, 2013 11:50 AM, <btc@openinworld.com
>> <mailto:btc@openinworld.com>> wrote:
>>
>> �� �� I am probably not working on it anytime soon, but btw I logged the
>> �� �� idea last week of enhancing Pharo Launcher with some kind of support
>> �� �� for bisect operations.
>> �� �� https://pharo.fogbugz.com/__default.asp?11927
>> �� �� <https://pharo.fogbugz.com/default.asp?11927>.
>>
>>
>> �� �� cheers -ben
>>
>> �� �� Goubier Thierry wrote:
>>
>> �� �� �� �� Hi all,
>>
>> �� �� �� �� I want to thank the combination of Pharo Launcher and the
>> �� �� �� �� pharo-core github repo for earching a specific bug in Pharo 3,
>> �� �� �� �� linked to https://pharo.fogbugz.com/f/__cases/11949/
>>
>> �� �� �� �� <https://pharo.fogbugz.com/f/cases/11949/> :
>>
>> �� �� �� �� I noticed that the bug was introduced between 30450 and 30490.
>> �� �� �� �� With the Pharo launcher, I then went through a ad-hoc bisecting
>> �� �� �� �� (loading the right image version / launching it / testing) :
>>
>> �� �� �� �� Start point is 30450 No bug, 30490 bug.
>>
>> �� �� �� �� 30470 No bug
>> �� �� �� �� 30480 No
>> �� �� �� �� 30485 Bug
>> �� �� �� �� 30483 No
>> �� �� �� �� 30484 Bug
>>
>> �� �� �� �� Then I tried to view the changes in Morphic for the bug out of
>> �� �� �� �� the Monticello tools... Didn't work :( It's hard to guess which
>> �� �� �� �� versions have changed and when in relation to the image version
>> �� �� �� �� number.
>>
>> �� �� �� �� So I went to github/pharo-core and I searched for the relevant
>> �� �� �� �� commit:
>>
>> �� �� �� �� https://github.com/pharo-__project/pharo-core/commit/__5034553d07f342a5a0e512757a04e6__afec677d96
>>
>> �� �� �� �� <https://github.com/pharo-project/pharo-core/commit/5034553d07f342a5a0e512757a04e6afec677d96>
>>
>>
>> �� �� �� �� And a file that could be relevant:
>>
>> �� �� �� �� https://github.com/pharo-__project/pharo-core/commit/__5034553d07f342a5a0e512757a04e6__afec677d96#diff-__8582177f7215f3cef75a8ce52f5ef0__12
>>
>> �� �� �� �� <https://github.com/pharo-project/pharo-core/commit/5034553d07f342a5a0e512757a04e6afec677d96#diff-8582177f7215f3cef75a8ce52f5ef012>
>>
>>
>> �� �� �� �� And there I could see things in relation with MorpTreeMorph...
>> �� �� �� �� Bug solved shortly thereafter. Damn Rectangle stuff :(
>>
>> �� �� �� �� Thanks again
>>
>>
>>
>
> --
> Thierry Goubier
> CEA list
> Laboratoire des Fondations des Syst��mes Temps R��el Embarqu��s
> 91191 Gif sur Yvette Cedex
> France
> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
>