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

2020-08-19 Thread 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 wi

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

2020-08-19 Thread 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 int

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

2020-08-19 Thread 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 sy

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

2020-08-19 Thread 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 possibilit

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

2020-08-19 Thread 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 t

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

2020-08-19 Thread 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. Mar

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

2020-08-19 Thread 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

[Pharo-users] PostgresV2 Driver available?

2020-08-19 Thread Esteban Maringolo
Hi, Is anybody using the "old" PostgresV2 driver in Pharo 8? I just checked in the pharo-rdbms/garage repository and of course everything is very old there. But I'm having a few issues with P3 that I didn't have before (with the PgV2) and I want to be test whether there is something related with

Re: [Pharo-users] CannotWriteData errors in P3 and Seaside

2020-08-19 Thread Esteban Maringolo
I kept looking into this, and still haven't found what might be causing it. However, I was trying to "salvage" that until I find a solution, and run a "healthcheck" to be sure that the GlorpSession has an active connection, and then I found that a P3Client reports as connected even when it's not.

Re: [Pharo-users] CannotWriteData errors in P3 and Seaside

2020-08-19 Thread Sven Van Caekenberghe
IIUC a socket stream does not automatically/automagically know that the state of the connection changed, unless/until it tries to use it (read or write to it, wait for data, ...). I would recommend using #isWorking to actually test if a connection is good, if you would need to do that. That doe

[Pharo-users] Iceberg "adopt commit" behavior

2020-08-19 Thread Esteban Maringolo
Hi, What does the "Adopt commit" mean? It seems like a rebase, but I'm not sure. I often have ongoing changes in my image, and also changes in the filesystem (css, js, Dockerfile, etc.). So what I do is to commit on the filesystem, and then "adopt" the recently created commit, and then commit in