- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Changes Browser is broken

by Ben Coman

I hadn't used Recover Changes for a while, but recently found that it had lost a lot of power. Particularly not being able to filter to show only the most recent updates. Its tedious to manually search for the latest version of several methods. cheers -ben On Fri, Mar 18, 2016 at 6:30 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Today I learned that you can actually lose code in Pharo because the record > is not always added to the changes file. > > Also using the tool is quite a lot of pain, so if you want to recover your > changes you have to do a lot of archaeology. > > I've added several issues and marked most of them as '2 - Really Important', > because I think they are (especially for students etc that like to break > things), but maybe you don't want it for Pharo 5. > > https://pharo.fogbugz.com/f/cases/17840/ChangesBrowser-selectAll-DNU > https://pharo.fogbugz.com/f/cases/17841/Creating-a-class-from-a-debugger-du… > https://pharo.fogbugz.com/f/cases/17842/Recover-lost-changes-doesn-t-recove… > https://pharo.fogbugz.com/f/cases/17843/Changes-Browser-doesn-t-recover-cha… > > Peter > >

March 17, 2016

Changes Browser is broken

by Peter UhnÃ¡k

Today I learned that you can actually lose code in Pharo because the record is not always added to the changes file. Also using the tool is quite a lot of pain, so if you want to recover your changes you have to do a lot of archaeology. I've added several issues and marked most of them as '2 - Really Important', because I think they are (especially for students etc that like to break things), but maybe you don't want it for Pharo 5. https://pharo.fogbugz.com/f/cases/17840/ChangesBrowser-selectAll-DNU https://pharo.fogbugz.com/f/cases/17841/Creating-a-class-from-a-debugger-du… https://pharo.fogbugz.com/f/cases/17842/Recover-lost-changes-doesn-t-recove… https://pharo.fogbugz.com/f/cases/17843/Changes-Browser-doesn-t-recover-cha… Peter

March 17, 2016

Re: [Pharo-dev] Loading an image crashes the VM

by Peter UhnÃ¡k

I got this error maybe once or twice maybe a year ago on linux, but I had a lot of windows opened (like 20 or 30), and when I got back to big screen it was ok again. Peter On Thu, Mar 17, 2016 at 8:51 PM, stepharo <stepharo(a)free.fr> wrote: > Jan > > I'm always switching monitor and I did not get it. > Are you on mac? > The bug I got is when I change manually the display extent: > There it crashes from time to time. > > Stef > > Le 17/3/16 18:14, Jan KurÅ¡ a Ã©crit : > > Hi, > > Looks like I know this bug. The problem is when you save the image on a > big screen (with external monitor) and try to open it on a small one > (without the external monitor). The same behaviour (for me) as in this case: > > > <https://pharo.fogbugz.com/f/cases/15944/Image-crash-on-Pharo-due-to-fonts-o…> > https://pharo.fogbugz.com/f/cases/15944/Image-crash-on-Pharo-due-to-fonts-o… > > Cheers, > Jan > > On Tue, Mar 15, 2016 at 10:48 PM Damien Pollet <damien.pollet(a)gmail.com> > wrote: > >> Any idea what version of the image should be relatively stable ? >> >> On 15 March 2016 at 07:31, Max Leske <maxleske(a)gmail.com> wrote: >> >>> I should have looked at the attachmentâ¦ What youâre seeing is a problem >>> with UFFI, Esteban is trying to hunt down the cause. For some reason the >>> font loading mechanism uses an FFI call that doesnât always do what itâs >>> supposed to. Usually this will lead to a playground or browser displaying a >>> red âsquare for deathâ after boot but Iâve also seen segfaults myself. >>> >>> This (very likely) has nothing to do with image size, as I suggested >>> earlier. >>> >>> Unfortunately, I donât think there is a fix at the moment other than >>> trying save a new copy of the image. >>> >>> Cheers, >>> Max >>> >>> >>> > On 15 Mar 2016, at 01:54, Ben Coman <btc(a)openInWorld.com> >>> <btc(a)openInWorld.com> wrote: >>> > >>> > On Tue, Mar 15, 2016 at 1:25 AM, Jan KurÅ¡ <kurs(a)inf.unibe.ch> wrote: >>> >> Hi, >>> >> >>> >> I am trying to open an image I saved a few days ago and I am getting >>> this >>> >> message (the whole log is attached): >>> >> >>> >> stack page bytes 4096 available headroom 2788 minimum unused headroom >>> 3020 >>> >> >>> >> (Segmentation fault) >>> >> >>> >> Anyone experiencing something similar? I am running the latest pharo5 >>> VM on >>> >> Linux. >>> >> >>> >> Cheers, >>> >> Jan >>> > >>> > Something similar happened to me for the first time last night, about >>> > three times in quick succession. Seemed to be when I started an Image >>> > from a shell and later killed it with control-C. Incidentally, these >>> > was with a recent Tracker image only an hour old for me, which had >>> > locked while I was doing risky changes to DelayScheduler, but I was >>> > surprised that it affected the Image on disk. I was doing temporary >>> > checkpoint saves just prior to Accepting risky code changes. Then upon >>> > restart I got the error. But I could not reliably reproduce the >>> > problem. >>> > >>> > Certainly it was not a large Image. >>> > >>> > VM: http://files.pharo.org/vm/pharo-spur32/linux/463.zip >>> > Image: >>> https://ci.inria.fr/pharo/view/5.0-Analysis/job/Pharo-5.0-Issue-Tracker-Ima… >>> > Platform: Debian 8 Jessie 32-bit >>> > >>> > cheers -ben >>> > >>> >>> >>> >> >> >> -- >> Damien Pollet >> type less, do more [ | ] http://people.untyped.org/damien.pollet >> > >

March 17, 2016

Re: [Pharo-dev] Loading an image crashes the VM

by stepharo

Jan I'm always switching monitor and I did not get it. Are you on mac? The bug I got is when I change manually the display extent: There it crashes from time to time. Stef Le 17/3/16 18:14, Jan KurÅ¡ a Ã©crit : > Hi, > Looks like I know this bug. The problem is when you save the image on > a big screen (with external monitor) and try to open it on a small one > (without the external monitor). The same behaviour (for me) as in this > case: > > https://pharo.fogbugz.com/f/cases/15944/Image-crash-on-Pharo-due-to-fonts-o… > > Cheers, > Jan > > On Tue, Mar 15, 2016 at 10:48 PM Damien Pollet > <damien.pollet(a)gmail.com <mailto:damien.pollet@gmail.com>> wrote: > > Any idea what version of the image should be relatively stable ? > > On 15 March 2016 at 07:31, Max Leske <maxleske(a)gmail.com > <mailto:maxleske@gmail.com>> wrote: > > I should have looked at the attachmentâ¦ What youâre seeing is > a problem with UFFI, Esteban is trying to hunt down the cause. > For some reason the font loading mechanism uses an FFI call > that doesnât always do what itâs supposed to. Usually this > will lead to a playground or browser displaying a red âsquare > for deathâ after boot but Iâve also seen segfaults myself. > > This (very likely) has nothing to do with image size, as I > suggested earlier. > > Unfortunately, I donât think there is a fix at the moment > other than trying save a new copy of the image. > > Cheers, > Max > > > > On 15 Mar 2016, at 01:54, Ben Coman <btc(a)openInWorld.com> wrote: > > > > On Tue, Mar 15, 2016 at 1:25 AM, Jan KurÅ¡ <kurs(a)inf.unibe.ch > <mailto:kurs@inf.unibe.ch>> wrote: > >> Hi, > >> > >> I am trying to open an image I saved a few days ago and I > am getting this > >> message (the whole log is attached): > >> > >> stack page bytes 4096 available headroom 2788 minimum > unused headroom 3020 > >> > >> (Segmentation fault) > >> > >> Anyone experiencing something similar? I am running the > latest pharo5 VM on > >> Linux. > >> > >> Cheers, > >> Jan > > > > Something similar happened to me for the first time last > night, about > > three times in quick succession. Seemed to be when I > started an Image > > from a shell and later killed it with control-C. > Incidentally, these > > was with a recent Tracker image only an hour old for me, > which had > > locked while I was doing risky changes to DelayScheduler, > but I was > > surprised that it affected the Image on disk. I was doing > temporary > > checkpoint saves just prior to Accepting risky code changes. > Then upon > > restart I got the error. But I could not reliably reproduce the > > problem. > > > > Certainly it was not a large Image. > > > > VM: http://files.pharo.org/vm/pharo-spur32/linux/463.zip > > Image: > https://ci.inria.fr/pharo/view/5.0-Analysis/job/Pharo-5.0-Issue-Tracker-Ima… > > Platform: Debian 8 Jessie 32-bit > > > > cheers -ben > > > > > > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet >

March 17, 2016

[pharo-project/pharo-core] 660d6d: 50651

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 660d6dda29c61609b7260e9d453d3e0695dcf95c https://github.com/pharo-project/pharo-core/commit/660d6dda29c61609b7260e9d… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-03-17 (Thu, 17 Mar 2016) Changed paths: M ConfigurationOfGTEventRecorder.package/ConfigurationOfGTEventRecorder.class/instance/symbolic versions/stable_.st A ConfigurationOfGTEventRecorder.package/ConfigurationOfGTEventRecorder.class/instance/versions/version012_.st M ConfigurationOfSessionManager.package/ConfigurationOfSessionManager.class/instance/symbolic versions/stable_.st A ConfigurationOfSessionManager.package/ConfigurationOfSessionManager.class/instance/versions/version14_.st R GT-EventRecorder.package/GTEventTool.class/instance/private/checkProcess.st R GT-EventRecorder.package/GTEventTool.class/instance/updating/update_.st M Polymorph-Widgets.package/Pharo3DarkTheme.class/class/settings/newDefaultSettings.st A Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/accessing colors/balloonBackgroundColor.st M Polymorph-Widgets.package/Pharo3Theme.class/class/settings/newDefaultSettings.st M Polymorph-Widgets.package/UITheme.class/class/accessing/current_.st R Polymorph-Widgets.package/UITheme.class/class/installing/installFullTheme.st A Polymorph-Widgets.package/UITheme.class/instance/accessing colors/balloonBackgroundColor.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50650.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50651.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50650.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50651.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Settings-Polymorph.package/PolymorphSystemSettings.class/class/morphic/uiThemeClass_.st M System-SessionManager.package/SessionManager.class/class/compatibility - startupList/initializedSessionManager.st M System-SessionManager.package/StartupUIManager.class/instance/error handling/handleError_log_.st Log Message: ----------- 50651 17836 GTEventTool>>#checkProcess has undeclared variables https://pharo.fogbugz.com/f/cases/17836 17834 World Morph is started up before Fonts https://pharo.fogbugz.com/f/cases/17834 16527 All popups very hard to read with white on lightblue https://pharo.fogbugz.com/f/cases/16527 http://files.pharo.org/image/50/50651.zip

March 17, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50651 Home: https://github.com/pharo-project/pharo-core

March 17, 2016

Re: [Pharo-dev] Loading an image crashes the VM

by Jan KurÅ¡

Hi, Looks like I know this bug. The problem is when you save the image on a big screen (with external monitor) and try to open it on a small one (without the external monitor). The same behaviour (for me) as in this case: https://pharo.fogbugz.com/f/cases/15944/Image-crash-on-Pharo-due-to-fonts-o… Cheers, Jan On Tue, Mar 15, 2016 at 10:48 PM Damien Pollet <damien.pollet(a)gmail.com> wrote: > Any idea what version of the image should be relatively stable ? > > On 15 March 2016 at 07:31, Max Leske <maxleske(a)gmail.com> wrote: > >> I should have looked at the attachmentâ¦ What youâre seeing is a problem >> with UFFI, Esteban is trying to hunt down the cause. For some reason the >> font loading mechanism uses an FFI call that doesnât always do what itâs >> supposed to. Usually this will lead to a playground or browser displaying a >> red âsquare for deathâ after boot but Iâve also seen segfaults myself. >> >> This (very likely) has nothing to do with image size, as I suggested >> earlier. >> >> Unfortunately, I donât think there is a fix at the moment other than >> trying save a new copy of the image. >> >> Cheers, >> Max >> >> >> > On 15 Mar 2016, at 01:54, Ben Coman <btc(a)openInWorld.com> wrote: >> > >> > On Tue, Mar 15, 2016 at 1:25 AM, Jan KurÅ¡ <kurs(a)inf.unibe.ch> wrote: >> >> Hi, >> >> >> >> I am trying to open an image I saved a few days ago and I am getting >> this >> >> message (the whole log is attached): >> >> >> >> stack page bytes 4096 available headroom 2788 minimum unused headroom >> 3020 >> >> >> >> (Segmentation fault) >> >> >> >> Anyone experiencing something similar? I am running the latest pharo5 >> VM on >> >> Linux. >> >> >> >> Cheers, >> >> Jan >> > >> > Something similar happened to me for the first time last night, about >> > three times in quick succession. Seemed to be when I started an Image >> > from a shell and later killed it with control-C. Incidentally, these >> > was with a recent Tracker image only an hour old for me, which had >> > locked while I was doing risky changes to DelayScheduler, but I was >> > surprised that it affected the Image on disk. I was doing temporary >> > checkpoint saves just prior to Accepting risky code changes. Then upon >> > restart I got the error. But I could not reliably reproduce the >> > problem. >> > >> > Certainly it was not a large Image. >> > >> > VM: http://files.pharo.org/vm/pharo-spur32/linux/463.zip >> > Image: >> https://ci.inria.fr/pharo/view/5.0-Analysis/job/Pharo-5.0-Issue-Tracker-Ima… >> > Platform: Debian 8 Jessie 32-bit >> > >> > cheers -ben >> > >> >> >> > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet >

March 17, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50650 Home: https://github.com/pharo-project/pharo-core

March 17, 2016

[pharo-project/pharo-core] c18da7: 50650

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: c18da766dd585504aa95dad28064460a9f4e1db4 https://github.com/pharo-project/pharo-core/commit/c18da766dd585504aa95dad2… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-03-17 (Thu, 17 Mar 2016) Changed paths: M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version47_.st M Glamour-FastTable.package/GLMFastTableDataSource.class/definition.st A Glamour-FastTable.package/GLMFastTableDataSource.class/instance/factory/editRowMorphForColumn_element_.st R Glamour-FastTable.package/GLMFastTableDataSource.class/instance/factory/modified_from_with_.st R Glamour-FastTable.package/GLMFastTableDataSource.class/instance/private/editRowMorphForColumn_element_.st R Glamour-FastTable.package/GLMFastTableDataSource.class/instance/private/forceStopStepping.st R Glamour-FastTable.package/GLMFastTableDataSource.class/instance/private/resetStopStepping.st R Glamour-FastTable.package/GLMFastTableDataSource.class/instance/stepping/shouldStopStepping.st R Glamour-FastTable.package/GLMFastTableDataSource.class/instance/stepping/stepTime.st R Glamour-FastTable.package/GLMFastTableDataSource.class/instance/stepping/wantsSteps.st R Glamour-FastTable.package/extension/FTTableMorph/instance/step.st R Glamour-FastTable.package/extension/FTTableMorph/instance/stepTime.st R Glamour-FastTable.package/extension/FTTableMorph/instance/wantsSteps.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50649.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50650.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50649.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50650.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50650 17837 Revert changes to fast table morph from glamour version 3.15 https://pharo.fogbugz.com/f/cases/17837 http://files.pharo.org/image/50/50650.zip

March 17, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50649 Home: https://github.com/pharo-project/pharo-core

March 17, 2016