- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Easy bug submission

by Andrey Larionov

http://code.google.com/p/support/wiki/IssueTracker#Issue_entry Some explanations from Google Code team On Mon, Oct 5, 2009 at 13:59, Andrey Larionov <anlarionov(a)gmail.com> wrote: > There is no API for Mantis, and it dosn't stop us from using > ensureFix: and others usefull features from Installer > > On Mon, Oct 5, 2009 at 13:48, Adrian Lienhard <adi(a)netstyle.ch> wrote: >> That would be nice. But is there an API for the Google issue tracker >> to create new reports? I had a look some time ago but didn't find any. >> >> Adrian >> >> On Oct 5, 2009, at 10:29 , Andrey Larionov wrote: >> >>> What about to add another button to error dialog? The button action >>> "Report bug", which gather debug info and ask user to provide >>> meaningful description of how to reproduce, and then posts this >>> information (maybe possibly search for duplicates entries) as defect >>> report in bugtracker. >>> >>> _______________________________________________ >>> 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 >> >

Oct. 5, 2009

Re: [Pharo-project] Easy bug submission

by Andrey Larionov

There is no API for Mantis, and it dosn't stop us from using ensureFix: and others usefull features from Installer On Mon, Oct 5, 2009 at 13:48, Adrian Lienhard <adi(a)netstyle.ch> wrote: > That would be nice. But is there an API for the Google issue tracker > to create new reports? I had a look some time ago but didn't find any. > > Adrian > > On Oct 5, 2009, at 10:29 , Andrey Larionov wrote: > >> What about to add another button to error dialog? The button action >> "Report bug", which gather debug info and ask user to provide >> meaningful description of how to reproduce, and then posts this >> information (maybe possibly search for duplicates entries) as defect >> report in bugtracker. >> >> _______________________________________________ >> 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 >

Oct. 5, 2009

Re: [Pharo-project] issue 996: analogousCodeTo:

by Henrik Johansen

For the stack top error, a better solution than adding asText to Object would be to implement: ContextVariablesInspector >> contents ^super contents printString It's a subclass of StringHolder for some reason, which explain why it doesn't exactly like that the ContextVariable can be any arbitrary object... Cheers, Henry On Oct 5, 2009, at 11:17 33AM, HernÃ¡n Morales Durand wrote: > Hi Ramiro, > You don't need to modify a method to open a debugger, hitting Alt + > . will do it. The behavior you describe is present in Pharo-Core > #10466 too and is probably the same when clicking the "stack top" item > in the Debugger right bottom pane (the context variables inspector). > I'm not fan at all of populating Object, but a quick workaround for > those who want to continue debugging without meta-debugging is to > define in Object > > asText > ^ self asString asText > > Cheers, > > HernÃ¡n > > 2009/10/5 Ramiro Diaz Trepat <ramiro(a)diaztrepat.name>: >> Sorry, and the way to reproduce was simply introducing a "self >> halt" in some >> method, or executing over a real bug as well, and trying to debug >> from >> there. >> Thanks again >> >> >> On Mon, Oct 5, 2009 at 8:47 AM, Ramiro Diaz Trepat <ramiro(a)diaztrepat.name >> > >> wrote: >>> >>> Hi Damien, thanks for answering. >>> The error happens on a the previous dev image (09.09.03) that was >>> updated >>> until yesterday night. >>> If I download the new dev image though, the error seems to go away. >>> I thought there was no difference, in theory at least, between an >>> updated >>> image and a freshly downloaded one. >>> Cheers >>> >>> r. >>> >>> >>> On Mon, Oct 5, 2009 at 12:41 AM, Damien Cassou <damien.cassou(a)gmail.com >>> > >>> wrote: >>>> >>>> 2009/10/4 Ramiro Diaz Trepat <ramiro(a)diaztrepat.name>: >>>>> I saw previous posts from Steph saying that this fix had already >>>>> been >>>>> pushed, but I have an image updated up to now and it does happen. >>>> >>>> Please provide a detailed process on how to reproduce. Telling us >>>> the >>>> image you used is of interest too. >>>> >>>> -- >>>> Damien Cassou >>>> http://damiencassou.seasidehosting.st >>>> >>>> "Lambdas are relegated to relative obscurity until Java makes them >>>> popular by not having them." James Iry >>>> >>>> _______________________________________________ >>>> 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

Oct. 5, 2009

Re: [Pharo-project] Easy bug submission

by Adrian Lienhard

That would be nice. But is there an API for the Google issue tracker to create new reports? I had a look some time ago but didn't find any. Adrian On Oct 5, 2009, at 10:29 , Andrey Larionov wrote: > What about to add another button to error dialog? The button action > "Report bug", which gather debug info and ask user to provide > meaningful description of how to reproduce, and then posts this > information (maybe possibly search for duplicates entries) as defect > report in bugtracker. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 5, 2009

Re: [Pharo-project] issue 996: analogousCodeTo:

by HernÃ¡n Morales Durand

Hi Ramiro, You don't need to modify a method to open a debugger, hitting Alt + . will do it. The behavior you describe is present in Pharo-Core #10466 too and is probably the same when clicking the "stack top" item in the Debugger right bottom pane (the context variables inspector). I'm not fan at all of populating Object, but a quick workaround for those who want to continue debugging without meta-debugging is to define in Object asText ^ self asString asText Cheers, HernÃ¡n 2009/10/5 Ramiro Diaz Trepat <ramiro(a)diaztrepat.name>: > Sorry, and the way to reproduce was simply introducing a "self halt" in some > method, or executing over a real bug as well, and trying to debug from > there. > Thanks again > > > On Mon, Oct 5, 2009 at 8:47 AM, Ramiro Diaz Trepat <ramiro(a)diaztrepat.name> > wrote: >> >> Hi Damien, thanks for answering. >> The error happens on a the previous dev image (09.09.03) that was updated >> until yesterday night. >> If I download the new dev image though, the error seems to go away. >> I thought there was no difference, in theory at least, between an updated >> image and a freshly downloaded one. >> Cheers >> >> r. >> >> >> On Mon, Oct 5, 2009 at 12:41 AM, Damien Cassou <damien.cassou(a)gmail.com> >> wrote: >>> >>> 2009/10/4 Ramiro Diaz Trepat <ramiro(a)diaztrepat.name>: >>> > I saw previous posts from Steph saying that this fix had already been >>> > pushed, but I have an image updated up to now and it does happen. >>> >>> Please provide a detailed process on how to reproduce. Telling us the >>> image you used is of interest too. >>> >>> -- >>> Damien Cassou >>> http://damiencassou.seasidehosting.st >>> >>> "Lambdas are relegated to relative obscurity until Java makes them >>> popular by not having them." James Iry >>> >>> _______________________________________________ >>> 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 >

Oct. 5, 2009

[Pharo-project] Easy bug submission

by Andrey Larionov

What about to add another button to error dialog? The button action "Report bug", which gather debug info and ask user to provide meaningful description of how to reproduce, and then posts this information (maybe possibly search for duplicates entries) as defect report in bugtracker.

Oct. 5, 2009

Re: [Pharo-project] issue 996: analogousCodeTo:

by Ramiro Diaz Trepat

Sorry, and the way to reproduce was simply introducing a "self halt" in some method, or executing over a real bug as well, and trying to debug from there.Thanks again On Mon, Oct 5, 2009 at 8:47 AM, Ramiro Diaz Trepat <ramiro(a)diaztrepat.name>wrote: > Hi Damien, thanks for answering. > The error happens on a the previous dev image (09.09.03) that was updated > until yesterday night. > If I download the new dev image though, the error seems to go away. > I thought there was no difference, in theory at least, between an updated > image and a freshly downloaded one. > Cheers > > > r. > > > > On Mon, Oct 5, 2009 at 12:41 AM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > >> 2009/10/4 Ramiro Diaz Trepat <ramiro(a)diaztrepat.name>: >> > I saw previous posts from Steph saying that this fix had already been >> > pushed, but I have an image updated up to now and it does happen. >> >> Please provide a detailed process on how to reproduce. Telling us the >> image you used is of interest too. >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Lambdas are relegated to relative obscurity until Java makes them >> popular by not having them." James Iry >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >

Oct. 5, 2009

Re: [Pharo-project] issue 996: analogousCodeTo:

by Ramiro Diaz Trepat

Hi Damien, thanks for answering. The error happens on a the previous dev image (09.09.03) that was updated until yesterday night. If I download the new dev image though, the error seems to go away. I thought there was no difference, in theory at least, between an updated image and a freshly downloaded one. Cheers r. On Mon, Oct 5, 2009 at 12:41 AM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > 2009/10/4 Ramiro Diaz Trepat <ramiro(a)diaztrepat.name>: > > I saw previous posts from Steph saying that this fix had already been > > pushed, but I have an image updated up to now and it does happen. > > Please provide a detailed process on how to reproduce. Telling us the > image you used is of interest too. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 5, 2009

Re: [Pharo-project] issue 996: analogousCodeTo:

by Damien Cassou

2009/10/4 Ramiro Diaz Trepat <ramiro(a)diaztrepat.name>: > I saw previous posts from Steph saying that this fix had already been > pushed, but I have an image updated up to now and it does happen. Please provide a detailed process on how to reproduce. Telling us the image you used is of interest too. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Oct. 4, 2009

Re: [Pharo-project] issue 996: analogousCodeTo:

by Ramiro Diaz Trepat

I saw previous posts from Steph saying that this fix had already been pushed, but I have an image updated up to now and it does happen.Cheers r. On Sun, Oct 4, 2009 at 11:39 PM, Ramiro Diaz Trepat <ramiro(a)diaztrepat.name>wrote: > Hi guys,My debugger casts exceptions as soon as I click on any stack point > and hence I can't almost use it for anything. > The error always seems to be this MNU ByteSymbol>>analogousCodeTo: > Is there a work around to use the debugger? > Thanks > > r >

Oct. 4, 2009