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 a
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
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 wi
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 int
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 sy
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 possibilit
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 t
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. Mar
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