August 2020 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Disable halt and breakpoints globally

by Steven Costiou

Le 2020-08-19 15:24, Esteban Maringolo a Ã©crit : > There is a similar view in Pharo 8, the Browse breakpoints show breakpoints and halts as well. The P8 view does not allow for dynamic activation, and that logic is only in P9. Steven. > However, I avoid using breakpoints because you cannot add/remove them within the debugger, and sometimes with nested blocks it is hard to specify which expression should get it. > > Regards! > > Esteban A. Maringolo > > On Wed, Aug 19, 2020 at 5:27 AM Steven Costiou <steven.costiou(a)kloum.io> wrote: > > So, I just checked and we have this view in Pharo 9 with all halts and breakpoints. > > We just need to put a global checkbox to (de)activate everything at once (and polish a little bit the view). > > Le 2020-08-19 10:11, Steven Costiou a Ã©crit : > > Hi, > > in Pharo 9/NewTools we added the possibility to disable a halt or a breakpoint through a checkbox in the inspector or from a view in the debugger. > For example this is an inspector on a test object: > > When a halt is disabled this way, it is still in your code but instead of halting it logs into the Transcript. > We planned to have a global view somewhere with a global "checkbox" to enable/disable them all. > But this will be only for Pharo 9. > > But to me it has interest only if you want to keep dormant debugging capabilities in production, that you awake when you have a problem that you need to debug. > Otherwise, I would do as Tim suggested and make sure there are no halts in the production image. > > Steven. > > Le 2020-08-18 22:46, Esteban Maringolo a Ã©crit : > Hi, > > I was bit by a bug in production I couldn't identify and it ended up > being a lost halt in the code that was hanging my whole image. So no > bug at all, a feature :-) > > Is there a way to disable the #halt and breakpoints? > This way I could add such an expression (if existent) to my server > startup and avoid issues like this. > > Regards! > > Esteban A. Maringolo

Aug. 19, 2020

Re: [Pharo-users] Disable halt and breakpoints globally

by Esteban Maringolo

There is a similar view in Pharo 8, the Browse breakpoints show breakpoints and halts as well. However, I avoid using breakpoints because you cannot add/remove them within the debugger, and sometimes with nested blocks it is hard to specify which expression should get it. Regards! Esteban A. Maringolo On Wed, Aug 19, 2020 at 5:27 AM Steven Costiou <steven.costiou(a)kloum.io> wrote: > So, I just checked and we have this view in Pharo 9 with all halts and > breakpoints. > > We just need to put a global checkbox to (de)activate everything at once > (and polish a little bit the view). > > > > Le 2020-08-19 10:11, Steven Costiou a Ã©crit : > > Hi, > > in Pharo 9/NewTools we added the possibility to disable a halt or a > breakpoint through a checkbox in the inspector or from a view in the > debugger. > For example this is an inspector on a test object: > > When a halt is disabled this way, it is still in your code but instead of > halting it logs into the Transcript. > We planned to have a global view somewhere with a global "checkbox" to > enable/disable them all. > But this will be only for Pharo 9. > > But to me it has interest only if you want to keep dormant debugging > capabilities in production, that you awake when you have a problem that you > need to debug. > Otherwise, I would do as Tim suggested and make sure there are no halts in > the production image. > > Steven. > > > > Le 2020-08-18 22:46, Esteban Maringolo a Ã©crit : > > Hi, > > I was bit by a bug in production I couldn't identify and it ended up > being a lost halt in the code that was hanging my whole image. So no > bug at all, a feature :-) > > Is there a way to disable the #halt and breakpoints? > This way I could add such an expression (if existent) to my server > startup and avoid issues like this. > > Regards! > > Esteban A. Maringolo > > > > >

Aug. 19, 2020

Re: [Pharo-users] Disable halt and breakpoints globally

by Esteban Maringolo

Hi Tim, For production I'm building a new Smalltalk image (and a Docker image as well) on each commit to master in my Gitlab repo. I was suggested to add Lint check to the build process in order to avoid being caught by something like this again. But the halt that got me was a notification from the Glorp cache telling the object that it was removed from it. So it was a particular condition that doesn't happen very often in my development image, and because I'm used to put halts here and there, ended up being commited and pushed to master. Best regards! Esteban A. Maringolo On Wed, Aug 19, 2020 at 3:24 AM Tim Mackinnon <tim(a)testit.works> wrote: > > Hi Esteban - its a good question (and I'm intrigued what can be done) - but for production aren't you automatically building a fresh image with a CI system... its pretty easy to do these days and this would stop that. Additionally you could add something to search for self halt, as a build step and fail your build on a non-zero result as well. > > Tim > > On Tue, 18 Aug 2020, at 9:46 PM, Esteban Maringolo wrote: > > Hi, > > > > I was bit by a bug in production I couldn't identify and it ended up > > being a lost halt in the code that was hanging my whole image. So no > > bug at all, a feature :-) > > > > Is there a way to disable the #halt and breakpoints? > > This way I could add such an expression (if existent) to my server > > startup and avoid issues like this. > > > > Regards! > > > > Esteban A. Maringolo > > > > >

Aug. 19, 2020

Re: [Pharo-users] Disable halt and breakpoints globally

by Steven Costiou

So, I just checked and we have this view in Pharo 9 with all halts and breakpoints. We just need to put a global checkbox to (de)activate everything at once (and polish a little bit the view). Le 2020-08-19 10:11, Steven Costiou a Ã©crit : > Hi, > > in Pharo 9/NewTools we added the possibility to disable a halt or a breakpoint through a checkbox in the inspector or from a view in the debugger. > For example this is an inspector on a test object: > > When a halt is disabled this way, it is still in your code but instead of halting it logs into the Transcript. > We planned to have a global view somewhere with a global "checkbox" to enable/disable them all. > But this will be only for Pharo 9. > > But to me it has interest only if you want to keep dormant debugging capabilities in production, that you awake when you have a problem that you need to debug. > Otherwise, I would do as Tim suggested and make sure there are no halts in the production image. > > Steven. > > Le 2020-08-18 22:46, Esteban Maringolo a Ã©crit : > >> Hi, >> >> I was bit by a bug in production I couldn't identify and it ended up >> being a lost halt in the code that was hanging my whole image. So no >> bug at all, a feature :-) >> >> Is there a way to disable the #halt and breakpoints? >> This way I could add such an expression (if existent) to my server >> startup and avoid issues like this. >> >> Regards! >> >> Esteban A. Maringolo

Aug. 19, 2020

Re: [Pharo-users] Disable halt and breakpoints globally

by StÃ©phane Ducasse

Hi Esteban We worked on being able to turn all the halt into dormant halt. (so that we could put a break point and toggle it when running scenario) Now I do not know the status of it. But the idea was nice. @thomas? @esteban What I would like is a simple widgets showing all the halts of the system package | class | method | and some actions to remove them or do something on them If you want to give a try doing this is Spec2 we will happily improve it and include it in Pharo. S > On 18 Aug 2020, at 22:46, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > Hi, > > I was bit by a bug in production I couldn't identify and it ended up > being a lost halt in the code that was hanging my whole image. So no > bug at all, a feature :-) > > Is there a way to disable the #halt and breakpoints? > This way I could add such an expression (if existent) to my server > startup and avoid issues like this. > > Regards! > > Esteban A. Maringolo > -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Aug. 19, 2020

Re: [Pharo-users] Disable halt and breakpoints globally

by Steven Costiou

Hi, in Pharo 9/NewTools we added the possibility to disable a halt or a breakpoint through a checkbox in the inspector or from a view in the debugger. For example this is an inspector on a test object: When a halt is disabled this way, it is still in your code but instead of halting it logs into the Transcript. We planned to have a global view somewhere with a global "checkbox" to enable/disable them all. But this will be only for Pharo 9. But to me it has interest only if you want to keep dormant debugging capabilities in production, that you awake when you have a problem that you need to debug. Otherwise, I would do as Tim suggested and make sure there are no halts in the production image. Steven. Le 2020-08-18 22:46, Esteban Maringolo a Ã©crit : > Hi, > > I was bit by a bug in production I couldn't identify and it ended up > being a lost halt in the code that was hanging my whole image. So no > bug at all, a feature :-) > > Is there a way to disable the #halt and breakpoints? > This way I could add such an expression (if existent) to my server > startup and avoid issues like this. > > Regards! > > Esteban A. Maringolo

Aug. 19, 2020

Re: [Pharo-users] Disable halt and breakpoints globally

by hogoww

I never tried it, but doesn't the command debugging >> "remove all breakpoints" fits for this purpose? Pierre On 19/08/2020 08:23, Tim Mackinnon wrote: > Hi Esteban - its a good question (and I'm intrigued what can be done) - but for production aren't you automatically building a fresh image with a CI system... its pretty easy to do these days and this would stop that. Additionally you could add something to search for self halt, as a build step and fail your build on a non-zero result as well. > > Tim > > On Tue, 18 Aug 2020, at 9:46 PM, Esteban Maringolo wrote: >> Hi, >> >> I was bit by a bug in production I couldn't identify and it ended up >> being a lost halt in the code that was hanging my whole image. So no >> bug at all, a feature :-) >> >> Is there a way to disable the #halt and breakpoints? >> This way I could add such an expression (if existent) to my server >> startup and avoid issues like this. >> >> Regards! >> >> Esteban A. Maringolo >> >>

Aug. 19, 2020

Re: [Pharo-users] Disable halt and breakpoints globally

by Tim Mackinnon

Hi Esteban - its a good question (and I'm intrigued what can be done) - but for production aren't you automatically building a fresh image with a CI system... its pretty easy to do these days and this would stop that. Additionally you could add something to search for self halt, as a build step and fail your build on a non-zero result as well. Tim On Tue, 18 Aug 2020, at 9:46 PM, Esteban Maringolo wrote: > Hi, > > I was bit by a bug in production I couldn't identify and it ended up > being a lost halt in the code that was hanging my whole image. So no > bug at all, a feature :-) > > Is there a way to disable the #halt and breakpoints? > This way I could add such an expression (if existent) to my server > startup and avoid issues like this. > > Regards! > > Esteban A. Maringolo > >

Aug. 19, 2020

Disable halt and breakpoints globally

by Esteban Maringolo

Hi, I was bit by a bug in production I couldn't identify and it ended up being a lost halt in the code that was hanging my whole image. So no bug at all, a feature :-) Is there a way to disable the #halt and breakpoints? This way I could add such an expression (if existent) to my server startup and avoid issues like this. Regards! Esteban A. Maringolo

Aug. 18, 2020

UK Smalltalk User Group meeting - Wednesday, August 26th

by Giovanni Corriga

The next meeting of the UK Smalltalk User Group will be on Wednesday, August 26th. In this meeting, Erik Stel will present his current project - CodeParadise. CodeParadise is a cloud based platform (to be) to learn to program using Object Oriented principles within a Smalltalk environment. CodeParadise is still in very early development, but some of its results have seen interest from the community. Therefore a presentation will provide insight in the design, current status, and possibilities of the results so far. The discussion afterwards can be used for both in-depth technical topics as well as the more philosophical topics about programming (as warmth and/or beer consumption will guide us). Given the current COVID-19 restrictions, this will be an online meeting from home. If you'd like to join us, please sign up in advance on the meeting's Meetup page https://www.meetup.com/UKSTUG/events/cbklbrybclbjc/ to receive the meeting details. Donât forget to bring your laptop and drinks! Cheers, Giovanni

Aug. 18, 2020