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

Re: [Pharo-dev] About the infinite debugger

by tesonep＠gmail.com

Yes, we have to check all the scenarios. The problems with the UI process is not resolved at all. On Tue, Aug 7, 2018 at 11:11 PM Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > I have more special cases where debugger hangs: > 19662 > <https://pharo.fogbugz.com/f/cases/19662/Debugger-step-through-mustBeBoolean…> > , 19928 > <https://pharo.fogbugz.com/f/cases/19928/Debugger-step-over-through-last-doI…> > , 20274 > <https://pharo.fogbugz.com/f/cases/20274/Debugger-infinite-recursion-when-te…> > . > They are still relevant > > 2018-08-07 22:01 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > >> Hi. >> >> Good job guys. I just checked my case 19848 >> <https://pharo.fogbugz.com/f/cases/19848/Step-over-or-though-expression-with…>. >> And it is now fixed. >> >> Thanks >> >> >> >> 2018-06-29 15:48 GMT+01:00 Guillermo Polito <guillermopolito(a)gmail.com>: >> >>> Hi all, >>> >>> during today's sprint we have been working with lots of people on the >>> infinite debugger problem (https://pharo.fogbugz.com/f/cases/22085/) >>> We have checked the emails sent in the latest month. Then, together with >>> Quentin, Pablo, Pavel, Yoan we have been discussing and testing hypothesis >>> all day. We have been also comparing the debuggers code between pharo 3/4 >>> (where the bug was is present) and pharo 7, but this was not necessarily >>> straight forward as the code is not the same and there is no easy diff... >>> >>> AAAAND, we have found that the problem may come from a wrong pragma >>> marker. Just removing that pragma gives us back the same behaviour as in >>> Pharo 3/4. :D >>> >>> https://github.com/pharo-project/pharo/pull/1621 >>> >>> I know that the exception handling/debugging has been modified several >>> times in the latest years (some refactorings, hiding contexts...), we >>> unfortunately don't have tests for it, so I'd like some more pair of eyes >>> on it. Ben, Martin could you take a look? >>> >>> Thanks all for the fish, >>> Guille >>> >> >> > -- Pablo Tesone. tesonep(a)gmail.com

Aug. 8, 2018

CI Down

by Guillermo Polito

Hi all, Since yesterday evening, CI is down because of Inria network problems at the level of Paris. Inria tells us that they do not have yet an estimation of how much time it will take to fix it. Until then, there will be no CI testing PRs nor new builds. Previous Pharo builds are still available in http://files.pharo.org/, which is hosted in OVH. I'll keep you updated, Guille

Aug. 8, 2018

Re: [Pharo-dev] Minheadless trial

by Esteban Lorenzano

Hi, > On 8 Aug 2018, at 09:33, Ben Coman <btc(a)openinworld.com> wrote: > > > > On 7 August 2018 at 13:47, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > Hi Ben, > > Sorry for coming here so late, I didnât see this thread before. > I already have a working minheadless branch that was adapted to Eliotâs process. > It was working for Pharo in Linux and Mac (Windows was ongoing but not finished, thatâs why is not pushed). > > You can find this branch here: > > https://github.com/estebanlm/opensmalltalk-vm/tree/add-minheadless-vm <https://github.com/estebanlm/opensmalltalk-vm/tree/add-minheadless-vm> > > I'll have a look at it. > > Interesting part is that I didnât tackled any of the issues you are working on, so the work is easily mergeable :) > > Cheers, > Esteban > > Ps: with some changes in image, Iâm using exclusively this VM since a couple of months and it works fine. > > That is good to know. So just to be clear... > even though its name indicates "headless", you are running a full graphical Image? Yes, using SDL2 and OSWindow (with some modifications). Advantages of Pharo investment on this, even in things that seemed useless at the beginning ;) Also, the minheadless VM has a âtraditional displayâ flag that will start a word too. > I got more curious about the original announcement saying... > "minheadless is a VM variant that unifies a lot of the code for Windows, Linux and OS X.â Yes, I like what Ronie did there, even if there is still work to do, but is cool. > > So here https://docs.google.com/spreadsheets/d/183GnSKZSMSEgVQZ0Fqa7-vITqKSpAlW_Axn… <https://docs.google.com/spreadsheets/d/183GnSKZSMSEgVQZ0Fqa7-vITqKSpAlW_Axn…> > I compare... > find "platforms/Win32/vm" -exec wc {} \; > find "platforms/Unix/vm" -exec wc {} \; > find "platforms/Mac OS/vm" -exec wc {} \; > to... > find "platforms/minheadless" -exec wc {} \; > > and if nothing important has been missed it seems about 30% of the original size. > I'd expect Ronie's effort to produce this should have a massive impact on future maintainability. It depends, but this is one of the reasons why we want to move into it. Our strategy is let the less possible in the VM (ideally, just the âcoreâ VM and a great FFI support), and move all the rest into the image. Esteban > > cheers -ben > > P.S. I excluded the following presuming its common before/after. > find "platforms/Cross/vm" -exec wc {} \; > btw, its about half the size of platforms/minheadless.

Aug. 8, 2018

Re: [Pharo-dev] Minheadless trial

by Ben Coman

On 7 August 2018 at 13:47, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi Ben, > > Sorry for coming here so late, I didnât see this thread before. > I already have a working minheadless branch that was adapted to Eliotâs > process. > It was working for Pharo in Linux and Mac (Windows was ongoing but not > finished, thatâs why is not pushed). > > You can find this branch here: > > https://github.com/estebanlm/opensmalltalk-vm/tree/add-minheadless-vm > I'll have a look at it. > Interesting part is that I didnât tackled any of the issues you are > working on, so the work is easily mergeable :) > > Cheers, > Esteban > > Ps: with some changes in image, Iâm using exclusively this VM since a > couple of months and it works fine. > That is good to know. So just to be clear... even though its name indicates "headless", you are running a full graphical Image? I got more curious about the original announcement saying... "minheadless is a VM variant that unifies a lot of the code for Windows, Linux and OS X." So here https://docs.google.com/spreadsheets/d/183GnSKZSMSEgVQZ0Fqa7-vITqKSpAlW_Axn… I compare... find "platforms/Win32/vm" -exec wc {} \; find "platforms/Unix/vm" -exec wc {} \; find "platforms/Mac OS/vm" -exec wc {} \; to... find "platforms/minheadless" -exec wc {} \; and if nothing important has been missed it seems about 30% of the original size. I'd expect Ronie's effort to produce this should have a massive impact on future maintainability. cheers -ben P.S. I excluded the following presuming its common before/after. find "platforms/Cross/vm" -exec wc {} \; btw, its about half the size of platforms/minheadless.

Aug. 8, 2018

Re: [Pharo-dev] About the infinite debugger

by Denis Kudriashov

I have more special cases where debugger hangs: 19662 <https://pharo.fogbugz.com/f/cases/19662/Debugger-step-through-mustBeBoolean…> , 19928 <https://pharo.fogbugz.com/f/cases/19928/Debugger-step-over-through-last-doI…> , 20274 <https://pharo.fogbugz.com/f/cases/20274/Debugger-infinite-recursion-when-te…> . They are still relevant 2018-08-07 22:01 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > Hi. > > Good job guys. I just checked my case 19848 > <https://pharo.fogbugz.com/f/cases/19848/Step-over-or-though-expression-with…>. > And it is now fixed. > > Thanks > > > > 2018-06-29 15:48 GMT+01:00 Guillermo Polito <guillermopolito(a)gmail.com>: > >> Hi all, >> >> during today's sprint we have been working with lots of people on the >> infinite debugger problem (https://pharo.fogbugz.com/f/cases/22085/) We >> have checked the emails sent in the latest month. Then, together with >> Quentin, Pablo, Pavel, Yoan we have been discussing and testing hypothesis >> all day. We have been also comparing the debuggers code between pharo 3/4 >> (where the bug was is present) and pharo 7, but this was not necessarily >> straight forward as the code is not the same and there is no easy diff... >> >> AAAAND, we have found that the problem may come from a wrong pragma >> marker. Just removing that pragma gives us back the same behaviour as in >> Pharo 3/4. :D >> >> https://github.com/pharo-project/pharo/pull/1621 >> >> I know that the exception handling/debugging has been modified several >> times in the latest years (some refactorings, hiding contexts...), we >> unfortunately don't have tests for it, so I'd like some more pair of eyes >> on it. Ben, Martin could you take a look? >> >> Thanks all for the fish, >> Guille >> > >

Aug. 7, 2018

Re: [Pharo-dev] About the infinite debugger

by Denis Kudriashov

Hi. Good job guys. I just checked my case 19848 <https://pharo.fogbugz.com/f/cases/19848/Step-over-or-though-expression-with…>. And it is now fixed. Thanks 2018-06-29 15:48 GMT+01:00 Guillermo Polito <guillermopolito(a)gmail.com>: > Hi all, > > during today's sprint we have been working with lots of people on the > infinite debugger problem (https://pharo.fogbugz.com/f/cases/22085/) We > have checked the emails sent in the latest month. Then, together with > Quentin, Pablo, Pavel, Yoan we have been discussing and testing hypothesis > all day. We have been also comparing the debuggers code between pharo 3/4 > (where the bug was is present) and pharo 7, but this was not necessarily > straight forward as the code is not the same and there is no easy diff... > > AAAAND, we have found that the problem may come from a wrong pragma > marker. Just removing that pragma gives us back the same behaviour as in > Pharo 3/4. :D > > https://github.com/pharo-project/pharo/pull/1621 > > I know that the exception handling/debugging has been modified several > times in the latest years (some refactorings, hiding contexts...), we > unfortunately don't have tests for it, so I'd like some more pair of eyes > on it. Ben, Martin could you take a look? > > Thanks all for the fish, > Guille >

Aug. 7, 2018

Re: [Pharo-dev] [rmod] About the infinite debugger

by Tim Mackinnon

Thanks Paul - Iâd forgotten about that option (been using the close all to right option). Itâs just jarring - but worse is that none of the debuggers (even the first one) having anything useful in them... other than the error msg in the title. So you have to start all over again. Still, it sounds like we are honing in on something. Tim Sent from my iPhone > On 7 Aug 2018, at 19:38, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > > Hi Tim, > > Just in the event you didn't know there is an option in the World menu to > close all the open debuggers. > > Its in the "Windows" section, about half way down. > > > Paul > > > > Tim Mackinnon wrote >> ... >> >> On the plus side - its rare that you crash you image and then have to >> recover changes - but its just annoying when it gets in the way of >> debugging. ITs not just all the windows, its also the fact that none of >> the debugger windows actually puts you in a useful stack where you can see >> the problem - they are all stuck on DNU with a single line stack. >> >> Tim >> >> ... > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Aug. 7, 2018

Re: [Pharo-dev] Iceberg: Cannot Clone Pharo Repository

by Eric Gade

This workaround has done the trick for me for the moment (for anyone reading: you clone manually and then in Iceberg select the repository from the local filesystem). However, I'm now getting a new authentication error when trying to clone directly from my updated fork (instead of loading from filesystem). It claims I have not provided a valid set of credentials and that I should link to my ssh key or use HTTPS as the fetch method. Problem is, I've selected HTTPS already! I'm attaching a screenshot. On Mon, Aug 6, 2018 at 4:27 AM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > As a workaround, maybe you can try updating your fork before cloning it > from Iceberg? > > $ git clone yourFork > $ git pull from-pharo > $ git push > > On Mon, Aug 6, 2018 at 10:26 AM Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> Hi Eric, >> >> Thanks for the report. I'm looking into it. >> >> On Sun, Aug 5, 2018 at 6:20 PM Eric Gade <eric.gade(a)gmail.com> wrote: >> >>> I am having (new) issues cloning my forked pharo repository in a fresh >>> P7 image for development. Git objects are pulled from the repository >>> successfully, but during the checkout phase the error posted below occurs >>> (I can also provide a fuel dump by request). >>> >>> Here is my current system: >>> OSX 10.13.1 (High Sierra) >>> Pharo 7.0 >>> Build information: Pharo-7.0+alpha.build.1159.sha. >>> 65cff7b3c78af7ecf3728abdd2f44bf0cbc8a548 (32 Bit) >>> >>> My fork: >>> https://github.com/darth-cheney/pharo >>> >>> Error Stack: >>> >>> ``` >>> IceUnknownCommit(Object)>>doesNotUnderstand: #adopt >>> IcePharoPlugin>>repositoryWillBeCreated: >>> [ :each | each repositoryWillBeCreated: aRepository ] in >>> IcePluginManager>>repositoryWillBeCreated: in Block: [ :each | each >>> repositoryWillBeCreated: aRepositor...etc... >>> Array(SequenceableCollection)>>do: >>> IcePluginManager>>repositoryWillBeCreated: >>> IceRepositoryCreator>>cloneRepository >>> [ self validate. >>> self isCloning >>> ifTrue: [ self cloneRepository ] >>> ifFalse: [ self addLocalRepository ] ] in IceRepositoryCreator>>createRepository >>> in Block: [ self validate.... >>> BlockClosure>>on:do: >>> IceRepositoryCreator>>createRepository >>> [ ^ IceRepositoryCreator new >>> repository: repository; >>> remote: (IceGitRemote url: self remoteUrl); >>> location: self projectLocation location; >>> createRepository ] in IceTipGitHubRepositoryPanel( >>> IceTipGitRepositoryPanel)>>newRepository in Block: [ ^ >>> IceRepositoryCreator new... >>> [ :bar | >>> bar label: aString. >>> aBlock value ] in MorphicUIManager(UIManager)>>informUser:during: in >>> Block: [ :bar | ... >>> [ :bar | aBlock value: bar ] in MorphicUIManager>>informUserDuring: in >>> Block: [ :bar | aBlock value: bar ] >>> BlockClosure>>cull: >>> [ ^ block cull: self ] in [ self prepareForRunning. >>> CurrentJob value: self during: [ ^ block cull: self ] ] in Job>>run in >>> Block: [ ^ block cull: self ] >>> [ activeProcess psValueAt: index put: anObject. >>> aBlock value ] in CurrentJob(DynamicVariable)>>value:during: in Block: >>> [ activeProcess psValueAt: index put: anObject.... >>> BlockClosure>>ensure: >>> CurrentJob(DynamicVariable)>>value:during: >>> CurrentJob class(DynamicVariable class)>>value:during: >>> [ self prepareForRunning. >>> CurrentJob value: self during: [ ^ block cull: self ] ] in Job>>run in >>> Block: [ self prepareForRunning.... >>> BlockClosure>>ensure: >>> Job>>run >>> MorphicUIManager(UIManager)>>displayProgress:from:to:during: >>> MorphicUIManager>>informUserDuring: >>> MorphicUIManager(UIManager)>>informUser:during: >>> IceTipGitHubRepositoryPanel(IceTipGitRepositoryPanel)>>newRepository >>> IceTipGitHubRepositoryPanel>>newRepository >>> IceTipRegisterRepositoryDialog>>doAccept >>> [ self doAccept. >>> true ] in IceTipRegisterRepositoryDialog(IceTipOptionDialog)>>accept in >>> Block: [ self doAccept.... >>> BlockClosure>>on:do: >>> IceTipRegisterRepositoryDialog(IceTipOptionDialog)>>accept >>> ``` >>> >>> -- >>> Eric >>> >> >> >> -- >> >> >> >> Guille Polito >> >> Research Engineer >> >> Centre de Recherche en Informatique, Signal et Automatique de Lille >> >> CRIStAL - UMR 9189 >> >> French National Center for Scientific Research - *http://www.cnrs.fr >> <http://www.cnrs.fr>* >> >> >> *Web:* *http://guillep.github.io* <http://guillep.github.io> >> >> *Phone: *+33 06 52 70 66 13 >> > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 > -- Eric

Aug. 7, 2018

Re: [Pharo-dev] [rmod] About the infinite debugger

by Paul DeBruicker

Hi Tim, Just in the event you didn't know there is an option in the World menu to close all the open debuggers. Its in the "Windows" section, about half way down. Paul Tim Mackinnon wrote > ... > > On the plus side - its rare that you crash you image and then have to > recover changes - but its just annoying when it gets in the way of > debugging. ITs not just all the windows, its also the fact that none of > the debugger windows actually puts you in a useful stack where you can see > the problem - they are all stuck on DNU with a single line stack. > > Tim > > ... -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Aug. 7, 2018

Re: [Pharo-dev] New Iceberg Version 1.2.1

by tesonep＠gmail.com

Only adding a small detail, the Metacello expression is used to generate the project that is offered. Also I see it as the Detached head status for projects that are loaded using Metacello. Maybe we should display the dirtiness in other way, but I think that is not a problem. It is normal that a project is marked dirty while used. Cheers On Tue, Aug 7, 2018 at 4:01 PM Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Hi, > > I'll write down some of the reasons of the project's design, like that I > can afterwards copy paste it in the wiki :). > > First, this design did not came up from an egg. We worked on it for about > two months. And it is thought to be backwards compatible and manage lots of > metacello particularities. It may have things that are perfectible, sure, > so let's discuss it. > > One of the main problems we saw in metacello, and that Iceberg inherited, > was the "source subdirectory" thing. This source directory had to be > specified in the CLIENT, meaning that every time we clone a repository we > should know by heart the directory chose by its developer. Moreover, we > lack a standard way to do it, so everybody does as he feels (root > directory, src, source, repository, mc....). > > This has some bad consequences: > - once a repository is referenced by some other project, it is more > complicated to change its source directory. Imagine that tomorrow we set as > standard that all git repos should have the code in src. Then voyage should > change. And all its clients too. > - Making a typo in the code subdirectory means sometimes super ugly > errors from metacello that are difficult to debug and understand (e.g., > "Cannot resolve BaselineOfMetacello WTF") > > Moreover, there was another problem that people started stumbling on: the > fact that iceberg got confused sometimes thinking that an empty project was > in filetree (to keep backwards compatibility with projects without a > .properties). > > So we decided that for this release we wanted to revert a bit that > situation. Think object: let's put the meta-data used to interpret a > project's structure inside the project itself. > The idea is that: > > - each project should contain both a .project and a .properties file. The > first can contain arbitrary project meta-data (such as the source > directory). The second contains the cypress properties, which are needed to > correctly interpret the code inside the source directory. > - a project without a .project file is an old project and cannot be > interpreted, because we don't know the source directory > - a project without a .properties file is an old project and is by > default transformed in a project with a #filetree properties file > - an old project cloned from iceberg detects the missing .project file > and gives the user the opportunity to declare it (and then commit it > explicitly) > - an old project cloned and loaded from a Metacello expression defining a > source directory will honnor the source directory defined in the Metacello > expression (for backwards compatibility, and we have ~500 tests about this). > > # About defaults values / forcing the user to define a project > > First, notice that even when the repositories you load are just marked as > "dirty". > This is because in memory we add a project to your repository. > But you're not forced to commit it. > Actually, you can still load packages and baselines from that repository > without committing. > > This is in line with Iceberg's "explicitness". We try to not do any > destructive operation without asking the user first (that's why we have > several preview windows for pushing, pulling, checkout, merge..., and why > contrastingly with monticello we show the committed changes on the commit > window...). So, instead of transparently "adding the file" we have decided > to modify the project in memory and let the user the responsibility to > commit that file. > > If there's a drawback, is that the repository is marked as dirty. Which is > a bit noisy, yes, but still I think it's not so bad compared with the > previous drawbacks. > To solve this, we could have some default values, yes, and only mark it as > dirty if the project does not follow the default value. > This could work, but right now all projects use different names for their > source directories. > So the question is, what would be a good default? I'd like to use 'src' > since this is short, well known and less alien (all these in the sense that > we do not lose anything and we have a lot to gain by using it). > However, not much repositories use 'src' so it will still produce a lot of > "noise"... > > But still! Committing that file is a one-time operation. Once people fix > their repositories adding the project meta-data, you will not see them > dirty anymore. So we can see this as a transition noise too... > > Of course, new ideas are welcome. I'll let Pablo and Esteban add their > points of view on this too. > Guille > -- Pablo Tesone. tesonep(a)gmail.com

Aug. 7, 2018