August 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Sign of Impending Iceberg Doom on Pharo 6.1

by Esteban Lorenzano

> On 24 Aug 2018, at 20:41, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > Le 24/08/2018 Ã 19:03, Sean P. DeNigris a Ã©crit : >> Sometimes while working in Iceberg on 6.1, I see a progress bar(s) like the >> following: >> <http://forum.world.st/file/t128965/Screenshot_2018-08-24_12.jpeg> >> >> This seems to usually signal that a crash is not far away. It's doubly >> concerning because there is no clear way to stop the troubled process >> (interrupts often bring up a debugger on something else) and because, since >> one is now unable to save any code, it's unclear how to start over easily in >> a new image. In an extreme scenario, I recently panicked during such an >> experience and accidentally clicked "Save" instead of "Save Asâ¦" resulting >> in an image that took hours worth of code (I know maybe not a great >> practice) with it to the grave. >> >> Any idea why this happens or what we might be able to do anything about it? >> >> p.s. I was so concerned that I immediately resolved to move to Pharo 7, but >> that turned out not to be an option do to the recently reported bug with >> extension methods (that don't exactly match the package name) >> >> > > Hi, > > IIRC the problem only happens when the commit windows is maximize. > Something happen, maybe the progress bar updating launch a redraw of the > morph, and if the iceberg window is under the progress bar it also try > to redraw it but for that it snapshots methods etc... > > When I did not maximized my windows and kept them in the center it was fine. Yes, afaik that problem was related with redrawing of some glamour lists and an infinite loop triggered by the old iceberg UI. Esteban > >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >> > > > -- > Cyril Ferlicot > https://ferlicot.fr >

Aug. 24, 2018

Re: [Pharo-dev] Sign of Impending Iceberg Doom on Pharo 6.1

by Cyril Ferlicot D.

Le 24/08/2018 Ã 19:03, Sean P. DeNigris a Ã©critÂ : > Sometimes while working in Iceberg on 6.1, I see a progress bar(s) like the > following: > <http://forum.world.st/file/t128965/Screenshot_2018-08-24_12.jpeg> > > This seems to usually signal that a crash is not far away. It's doubly > concerning because there is no clear way to stop the troubled process > (interrupts often bring up a debugger on something else) and because, since > one is now unable to save any code, it's unclear how to start over easily in > a new image. In an extreme scenario, I recently panicked during such an > experience and accidentally clicked "Save" instead of "Save Asâ¦" resulting > in an image that took hours worth of code (I know maybe not a great > practice) with it to the grave. > > Any idea why this happens or what we might be able to do anything about it? > > p.s. I was so concerned that I immediately resolved to move to Pharo 7, but > that turned out not to be an option do to the recently reported bug with > extension methods (that don't exactly match the package name) > > Hi, IIRC the problem only happens when the commit windows is maximize. Something happen, maybe the progress bar updating launch a redraw of the morph, and if the iceberg window is under the progress bar it also try to redraw it but for that it snapshots methods etc... When I did not maximized my windows and kept them in the center it was fine. > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > -- Cyril Ferlicot https://ferlicot.fr

Aug. 24, 2018

Re: [Pharo-dev] Sign of Impending Iceberg Doom on Pharo 6.1

by Esteban Lorenzano

Hi, Please take into account that the iceberg version present on Pharo 6.1 is obsolete and most of the problems seen there should be solved in the version present on Pharo 7. You would ask why being an obsolete version we do not backport the good version for Pharo 6.1 and the answer is: Iceberg 1+ is a huge change and it may broke current P6.1 behaviour so we (I) decided not to do it. Instead, people using intensively iceberg are recommended to install themselves the correct version following the instructions here: https://github.com/pharo-vcs/iceberg#update-iceberg <https://github.com/pharo-vcs/iceberg#update-iceberg> <https://github.com/pharo-vcs/iceberg#update-iceberg> <https://github.com/pharo-vcs/iceberg#update-iceberg>Cheers, Esteban > On 24 Aug 2018, at 19:45, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > > I ve'seen this problem also but never been able to find a reproducible case. I've recall to see it even before Iceberg, so to me it looks like some Monticello issue. I always had the impression that Monticello it's trying to regenerate all the code definitions instead of the changes. Running exactly the same code snippet again usually worked for me. > > Anyways if someone had a reproducible case just let us know. > > On Fri, Aug 24, 2018 at 2:03 PM Sean P. DeNigris <sean(a)clipperadams.com <mailto:sean@clipperadams.com>> wrote: > Sometimes while working in Iceberg on 6.1, I see a progress bar(s) like the > following: > <http://forum.world.st/file/t128965/Screenshot_2018-08-24_12.jpeg <http://forum.world.st/file/t128965/Screenshot_2018-08-24_12.jpeg>> > > This seems to usually signal that a crash is not far away. It's doubly > concerning because there is no clear way to stop the troubled process > (interrupts often bring up a debugger on something else) and because, since > one is now unable to save any code, it's unclear how to start over easily in > a new image. In an extreme scenario, I recently panicked during such an > experience and accidentally clicked "Save" instead of "Save Asâ¦" resulting > in an image that took hours worth of code (I know maybe not a great > practice) with it to the grave. > > Any idea why this happens or what we might be able to do anything about it? > > p.s. I was so concerned that I immediately resolved to move to Pharo 7, but > that turned out not to be an option do to the recently reported bug with > extension methods (that don't exactly match the package name) > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html> >

Aug. 24, 2018

Re: [Pharo-dev] Sign of Impending Iceberg Doom on Pharo 6.1

by Gabriel Cotelli

I ve'seen this problem also but never been able to find a reproducible case. I've recall to see it even before Iceberg, so to me it looks like some Monticello issue. I always had the impression that Monticello it's trying to regenerate all the code definitions instead of the changes. Running exactly the same code snippet again usually worked for me. Anyways if someone had a reproducible case just let us know. On Fri, Aug 24, 2018 at 2:03 PM Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Sometimes while working in Iceberg on 6.1, I see a progress bar(s) like the > following: > <http://forum.world.st/file/t128965/Screenshot_2018-08-24_12.jpeg> > > This seems to usually signal that a crash is not far away. It's doubly > concerning because there is no clear way to stop the troubled process > (interrupts often bring up a debugger on something else) and because, since > one is now unable to save any code, it's unclear how to start over easily > in > a new image. In an extreme scenario, I recently panicked during such an > experience and accidentally clicked "Save" instead of "Save Asâ¦" resulting > in an image that took hours worth of code (I know maybe not a great > practice) with it to the grave. > > Any idea why this happens or what we might be able to do anything about it? > > p.s. I was so concerned that I immediately resolved to move to Pharo 7, but > that turned out not to be an option do to the recently reported bug with > extension methods (that don't exactly match the package name) > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > >

Aug. 24, 2018

Re: [Pharo-dev] Sign of Impending Iceberg Doom on Pharo 6.1

by Eliot Miranda

Hi Sean, On Fri, Aug 24, 2018 at 10:03 AM Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Sometimes while working in Iceberg on 6.1, I see a progress bar(s) like the > following: > <http://forum.world.st/file/t128965/Screenshot_2018-08-24_12.jpeg> > > This seems to usually signal that a crash is not far away. It's doubly > concerning because there is no clear way to stop the troubled process > (interrupts often bring up a debugger on something else) and because, since > one is now unable to save any code, it's unclear how to start over easily > in > a new image. In an extreme scenario, I recently panicked during such an > experience and accidentally clicked "Save" instead of "Save Asâ¦" resulting > in an image that took hours worth of code (I know maybe not a great > practice) with it to the grave. > > Any idea why this happens or what we might be able to do anything about it? > No. Yes. Indirectly I hope to help debug this. I am nearly finished with an error handling facility in the VM for FFI calls that will fail an FFI callout primitive with an error code indicating the kind of exception and the pc. This should at least stop the system from crashing and give us an improved ability to make sense of the exception; at least we'll be able to examine the arguments to the call. More details as I roll out the facility. It will require integrating some support code, rewriting FFI callout signatures to include an error code, etc. p.s. I was so concerned that I immediately resolved to move to Pharo 7, but > that turned out not to be an option do to the recently reported bug with > extension methods (that don't exactly match the package name) > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html _,,,^..^,,,_ best, Eliot

Aug. 24, 2018

Sign of Impending Iceberg Doom on Pharo 6.1

by Sean P. DeNigris

Sometimes while working in Iceberg on 6.1, I see a progress bar(s) like the following: <http://forum.world.st/file/t128965/Screenshot_2018-08-24_12.jpeg> This seems to usually signal that a crash is not far away. It's doubly concerning because there is no clear way to stop the troubled process (interrupts often bring up a debugger on something else) and because, since one is now unable to save any code, it's unclear how to start over easily in a new image. In an extreme scenario, I recently panicked during such an experience and accidentally clicked "Save" instead of "Save Asâ¦" resulting in an image that took hours worth of code (I know maybe not a great practice) with it to the grave. Any idea why this happens or what we might be able to do anything about it? p.s. I was so concerned that I immediately resolved to move to Pharo 7, but that turned out not to be an option do to the recently reported bug with extension methods (that don't exactly match the package name) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Aug. 24, 2018

Re: [Pharo-dev] Extension methods in p7

by Sean P. DeNigris

NorbertHartl wrote > https://github.com/pharo-project/pharo/pull/1685/files I'll try to review today. I tried to port a project to Pharo 7, but this bug made it unbearable. IMHO recategorizing methods is *not* the way to go. Let's just fix the bug! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Aug. 24, 2018

Re: [Pharo-dev] Startup Error in Recent Pharo 7

by Sean P. DeNigris

Update: It succeeded with a GH URL. The two scenarios that seemed to fail were: 1. a filetree URL 2. If I accidentally opened the same image twice via Launcher Still investigatingâ¦ ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Aug. 23, 2018

Startup Error in Recent Pharo 7

by Sean P. DeNigris

Did something change in the last two or three days with Iceberg/Metcello/Monticello? I was loading a project successfully in a startup script via: Metacello new repository: 'filetree://', (repoFolder / 'src') fullName; baseline: 'DeNigrisPreferences'; onConflict: [ :ex | ex allow ]; load. That now fails with "IceCloneLocationAlreadyExists": IceGenericError: '~/Dynabook/Working Images/MM 23 1021/pharo-local/iceberg/seandenigris/Pharo-Preferences' exists and is not an empty directory. The crazy thing is that the directory does *not* exist! This only fails at startup. If I run manually after startup, the load succeeds. Ideas? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Aug. 23, 2018

Re: [Pharo-dev] PharoLauncher : Image version determination error

by Sean P. DeNigris

demarey wrote > I just published a new version of the launcher Thanks! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Aug. 23, 2018