- Pharo-dev - lists.pharo.org

Esteban's ChangeLog week of 29 January 2018

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 29 January 2018 to 4 February 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=29/1/2018&to=4/2/2018 ChangeLog ========= 29 January 2018: ---------------- * I spent the morning adding certificates to the VM to sign it :) Next batch of VMs should come signed... now it rest to see if we need to sign the images also. cheers! Esteban

Feb. 5, 2018

git workflow (iceberg) and monticello packages

by Nicolai Hess

Hi , I am still not sure I understand the git based development workflow. I set up my image and repository as described by the guide. now, if new commits are in the pharo-project, iceberg shows the list of incoming changes (commits). Ok, but: If I modify code in my image (for example, change a method in class Morph), the morphic-core package is marked as dirty in monticello and my pharo repository in iceberg is marked with an asterisk. If I choose "synchronize repository ..." I would expect my change to be an uncommited change, but instead, it isn't shown and the Morphic-core package isn't dirty anymore. Is it because I need to create a branch first ? But why is the Morphic-core package not dirty anymore, the change is not commited or published, how do I know where are my changes ? nicolai

Feb. 4, 2018

[Pharo 7.0-dev] Build #498: 20937-Add-horizontal-scrollbar-to-FastTable

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #498 was: SUCCESS. The Pull Request #657 was integrated: "20937-Add-horizontal-scrollbar-to-FastTable" Pull request url: https://github.com/pharo-project/pharo/pull/657 Issue Url: https://pharo.fogbugz.com/f/cases/20937 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 4, 2018

[Pharo 7.0-dev] Build #497: 20124-FTTreeFunctionStrategy-call-deprecated-method

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #497 was: FAILURE. The Pull Request #796 was integrated: "20124-FTTreeFunctionStrategy-call-deprecated-method" Pull request url: https://github.com/pharo-project/pharo/pull/796 Issue Url: https://pharo.fogbugz.com/f/cases/20124 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 4, 2018

[Pharo 7.0-dev] Build #496: 21227-MBCommandrepositoryOfPackageNamed-sends-MCCacheRepository-default

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #496 was: FAILURE. The Pull Request #795 was integrated: "21227-MBCommandrepositoryOfPackageNamed-sends-MCCacheRepository-default" Pull request url: https://github.com/pharo-project/pharo/pull/795 Issue Url: https://pharo.fogbugz.com/f/cases/21227 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 4, 2018

Re: [Pharo-dev] Feedback about "Contribute a Fix to Pharo" (For windows users)

by Esteban Lorenzano

H, :( I think the old VM isâ¦ old. I need to promote new stables but I was waiting still a bit (something I see I canât do). Can you try with the latest vm? wget -O- get.pharo.org/vmLatest70 <http://get.pharo.org/vmLatest70> | bash > On 4 Feb 2018, at 02:34, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > And sometimes I get a debugger: > > <grafik.png> > > > And btw, the diff pane > "Left: working copy / Right: incoming updates" > > This is wrong, the working copy is on the right, no ? > > > > 2018-02-04 2:12 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>>: > > > 2018-02-03 19:54 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > > >> On 3 Feb 2018, at 17:09, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com <mailto:hernan.morales@gmail.com>> wrote: >> >> Hi Nicolai, >> >> 2018-02-03 10:42 GMT-03:00 Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>>: >>> The setup finally somehow works: >>> >>> I followed the guide at >>> https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo <https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo> >>> >>> * wget -O- get.pharo.org/70+vm <http://get.pharo.org/70+vm> | bash >>> >>> Does not work (windows msys-console) >>> It starts donwloading something but not pharo > > this is very weird, I will check. > >>> >>> I tried to do at seperate steps: >>> Only the image >>> * wget -O- get.pharo.org/70 <http://get.pharo.org/70> | bash >>> >>> Works >>> >>> * wget -O- get.pharo.org/vm <http://get.pharo.org/vm> | bash >>> >>> works, but is the wrong VM I guess, I can not open the image >>> >>> * wget -O- get.pharo.org/vm70 <http://get.pharo.org/vm70> | bash >>> >>> works, seems to load the right vm >>> >>> * ./pharo-ui Pharo.image >>> >>> Starts the vm but complains about : >>> "Pharo cannot write to the changes file named u:\tmp\pharo\Pharo.changes." >>> >>> I am sure the file is writable. >>> >>> The vm reports to be built on aug 27 2017, is this right? >>> >> >> I think is this one: >> >> https://pharo.fogbugz.com/f/cases/20805/Cannot-write-to-the-changes-file-er… <https://pharo.fogbugz.com/f/cases/20805/Cannot-write-to-the-changes-file-er…> > > yes, this is a known bug that we need to fix soon. > >>> Setting up Iceberg: >>> Yes, need option 2, that is, I use the commandline to clone a repository and >>> add it to iceberg. Cloning from iceberg directly does not work (long file >>> names). > > that should not be anymore an issue (since we migrated to tonel). > but cloning in disk is faster :) > >>> Ok, >>> now I see some uncommitted changes, the guide says: "you may need to invoke >>> synchronize" >>> >>> But how? >>> There is a "synchronize repository... " and "Synchronize full repository >>> ..." >>> menu entry. >>> >>> Which one? >>> The first synchronize does not show me how to actually do anything >>> and the second one shows a intimidating warning :) >>> FInally I removed my fork (it was pretty old), did a new fork and sstarted >>> with >>> a fresh image. > > I fixed thatâ¦ it should be the first synchronize. But you do not have to do anything other than execute it ;) > anyway, what I need to do is to put a note of what happens if (as you) your fork is too old: in that case you can go to Pharo/Synchronize repositories (but anyway, you do not need itâ¦ creating a branch from fogbugz issue will do a fetch and put you in the right place). > > >>> >>> Finally, the initial setup up is done, I now try to do some work with it >>> and report back > > thanks! > I hope everything goes smooth :) > > Not that smooth. The view for pull requests is still problematic, it seems to do alot in the background on > resizing the window (it is slow, does it do some lgit-calls on every window change ?) . > And it crashes often. yes, we are working on a revamp of UI that will hopefully fix all this (the crashes still should not happen :). cheers! Esteban > > <grafik.png> > > > cheers! > Esteban > >>> >>> >>> nicolai >>> >> > > >

Feb. 4, 2018

Re: [Pharo-dev] Feedback about "Contribute a Fix to Pharo" (For windows users)

by HernÃ¡n Morales Durand

I think the page needs more structure. This is how I see it: 0.1) Download and launch latest 7.0 pharo 0.2) Fork the Pharo repository 0.3) Setup Iceberg 0.3.1) Option 1: if you want to clone a fresh pharo repository 0.3.2) Option 2: if you make (or already have) an external pharo clone 0.3.3) Import your clone into iceberg 0.3.4) Tell iceberg about pharo-project 1) Opening an issue 2) Work on your image and push your change 3) Issue a pull request 4) Follow your pull request 5) Once your pull request is integrated Also it would help a lot for people reporting where is stuck. Cheers, HernÃ¡n 2018-02-03 22:38 GMT-03:00 Nicolai Hess <nicolaihess(a)gmail.com>: > Do we have a video tutorial, something like the one we had for the old-way > ? > I would like to see how others are using iceberg to review a change. > > > > > 2018-02-04 2:34 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > >> And sometimes I get a debugger: >> >> [image: Inline-Bild 1] >> >> >> And btw, the diff pane >> "Left: working copy / Right: incoming updates" >> >> This is wrong, the working copy is on the right, no ? >> >> >> >> 2018-02-04 2:12 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: >> >>> >>> >>> 2018-02-03 19:54 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>> >>>> >>>> >>>> On 3 Feb 2018, at 17:09, HernÃ¡n Morales Durand < >>>> hernan.morales(a)gmail.com> wrote: >>>> >>>> Hi Nicolai, >>>> >>>> 2018-02-03 10:42 GMT-03:00 Nicolai Hess <nicolaihess(a)gmail.com>: >>>> >>>> The setup finally somehow works: >>>> >>>> I followed the guide at >>>> https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo >>>> >>>> * wget -O- get.pharo.org/70+vm | bash >>>> >>>> >>>> Does not work (windows msys-console) >>>> It starts donwloading something but not pharo >>>> >>>> >>>> this is very weird, I will check. >>>> >>>> >>>> I tried to do at seperate steps: >>>> Only the image >>>> * wget -O- get.pharo.org/70 | bash >>>> >>>> Works >>>> >>>> * wget -O- get.pharo.org/vm | bash >>>> >>>> works, but is the wrong VM I guess, I can not open the image >>>> >>>> * wget -O- get.pharo.org/vm70 | bash >>>> >>>> works, seems to load the right vm >>>> >>>> * ./pharo-ui Pharo.image >>>> >>>> Starts the vm but complains about : >>>> "Pharo cannot write to the changes file named >>>> u:\tmp\pharo\Pharo.changes." >>>> >>>> I am sure the file is writable. >>>> >>>> The vm reports to be built on aug 27 2017, is this right? >>>> >>>> >>>> I think is this one: >>>> >>>> https://pharo.fogbugz.com/f/cases/20805/Cannot-write-to-the- >>>> changes-file-error-on-Windows >>>> >>>> >>>> yes, this is a known bug that we need to fix soon. >>>> >>>> Setting up Iceberg: >>>> Yes, need option 2, that is, I use the commandline to clone a >>>> repository and >>>> add it to iceberg. Cloning from iceberg directly does not work (long >>>> file >>>> names). >>>> >>>> >>>> that should not be anymore an issue (since we migrated to tonel). >>>> but cloning in disk is faster :) >>>> >>>> Ok, >>>> now I see some uncommitted changes, the guide says: "you may need to >>>> invoke >>>> synchronize" >>>> >>>> But how? >>>> There is a "synchronize repository... " and "Synchronize full repository >>>> ..." >>>> menu entry. >>>> >>>> Which one? >>>> The first synchronize does not show me how to actually do anything >>>> and the second one shows a intimidating warning :) >>>> FInally I removed my fork (it was pretty old), did a new fork and >>>> sstarted >>>> with >>>> a fresh image. >>>> >>>> >>>> I fixed thatâ¦ it should be the first synchronize. But you do not have >>>> to do anything other than execute it ;) >>>> anyway, what I need to do is to put a note of what happens if (as you) >>>> your fork is too old: in that case you can go to Pharo/Synchronize >>>> repositories (but anyway, you do not need itâ¦ creating a branch from >>>> fogbugz issue will do a fetch and put you in the right place). >>>> >>>> >>>> >>>> Finally, the initial setup up is done, I now try to do some work with it >>>> and report back >>>> >>>> >>>> thanks! >>>> I hope everything goes smooth :) >>>> >>> >>> Not that smooth. The view for pull requests is still problematic, it >>> seems to do alot in the background on >>> resizing the window (it is slow, does it do some lgit-calls on every >>> window change ?) . >>> And it crashes often. >>> >>> [image: Inline-Bild 1] >>> >>> >>>> >>>> cheers! >>>> Esteban >>>> >>>> >>>> >>>> nicolai >>>> >>>> >>>> >>>> >>> >> >

Feb. 4, 2018

Re: [Pharo-dev] Feedback about "Contribute a Fix to Pharo" (For windows users)

by HernÃ¡n Morales Durand

Hi 2018-02-03 15:54 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > > On 3 Feb 2018, at 17:09, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> > wrote: > > Hi Nicolai, > > 2018-02-03 10:42 GMT-03:00 Nicolai Hess <nicolaihess(a)gmail.com>: > > The setup finally somehow works: > > I followed the guide at > https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo > > * wget -O- get.pharo.org/70+vm | bash > > > Does not work (windows msys-console) > It starts donwloading something but not pharo > > > this is very weird, I will check. > > I checked and it works. > I tried to do at seperate steps: > Only the image > * wget -O- get.pharo.org/70 | bash > > Works > > * wget -O- get.pharo.org/vm | bash > > works, but is the wrong VM I guess, I can not open the image > > * wget -O- get.pharo.org/vm70 | bash > > works, seems to load the right vm > > * ./pharo-ui Pharo.image > > Starts the vm but complains about : > "Pharo cannot write to the changes file named u:\tmp\pharo\Pharo.changes." > > I am sure the file is writable. > > The vm reports to be built on aug 27 2017, is this right? > > > I think is this one: > > https://pharo.fogbugz.com/f/cases/20805/Cannot-write-to-the-changes-file-er… > > > yes, this is a known bug that we need to fix soon. > > Setting up Iceberg: > Yes, need option 2, that is, I use the commandline to clone a repository and > add it to iceberg. Cloning from iceberg directly does not work (long file > names). > > > that should not be anymore an issue (since we migrated to tonel). > but cloning in disk is faster :) I used the "Create repository" button in the Clone repository dialog, and the error in the attached screenshot is raised. As I reported a couple of days ago in the Pillar thread, you have to add $: to drive letter using MinGW: IceCredentialsProvider useCustomSsh: true. IceCredentialsProvider sshCredentials publicKey: '/c:/Users/[MY_USERNAME]/.ssh/id_rsa.pub'; privateKey: '/c:/Users/[MY_USERNAME]/.ssh/id_rsa' Also if I add "Code subdirectory: src" Iceberg shows "Code directory missing" > > Ok, > now I see some uncommitted changes, the guide says: "you may need to invoke > synchronize" > > But how? > There is a "synchronize repository... " and "Synchronize full repository > ..." > menu entry. > > Which one? > The first synchronize does not show me how to actually do anything > and the second one shows a intimidating warning :) I thought exactly the same. It opens a non-modal window titled "Synchronizing" but Process Browser didn't how any related process. > FInally I removed my fork (it was pretty old), did a new fork and sstarted > with > a fresh image. > > > I fixed thatâ¦ it should be the first synchronize. But you do not have to do > anything other than execute it ;) > anyway, what I need to do is to put a note of what happens if (as you) your > fork is too old: in that case you can go to Pharo/Synchronize repositories > (but anyway, you do not need itâ¦ creating a branch from fogbugz issue will > do a fetch and put you in the right place). > > > > Finally, the initial setup up is done, I now try to do some work with it > and report back > > > thanks! > I hope everything goes smooth :) > > cheers! > Esteban > > > > nicolai > > >

Feb. 4, 2018

Re: [Pharo-dev] Feedback about "Contribute a Fix to Pharo" (For windows users)

by Nicolai Hess

Do we have a video tutorial, something like the one we had for the old-way ? I would like to see how others are using iceberg to review a change. 2018-02-04 2:34 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > And sometimes I get a debugger: > > [image: Inline-Bild 1] > > > And btw, the diff pane > "Left: working copy / Right: incoming updates" > > This is wrong, the working copy is on the right, no ? > > > > 2018-02-04 2:12 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > >> >> >> 2018-02-03 19:54 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> >>> >>> On 3 Feb 2018, at 17:09, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> >>> wrote: >>> >>> Hi Nicolai, >>> >>> 2018-02-03 10:42 GMT-03:00 Nicolai Hess <nicolaihess(a)gmail.com>: >>> >>> The setup finally somehow works: >>> >>> I followed the guide at >>> https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo >>> >>> * wget -O- get.pharo.org/70+vm | bash >>> >>> >>> Does not work (windows msys-console) >>> It starts donwloading something but not pharo >>> >>> >>> this is very weird, I will check. >>> >>> >>> I tried to do at seperate steps: >>> Only the image >>> * wget -O- get.pharo.org/70 | bash >>> >>> Works >>> >>> * wget -O- get.pharo.org/vm | bash >>> >>> works, but is the wrong VM I guess, I can not open the image >>> >>> * wget -O- get.pharo.org/vm70 | bash >>> >>> works, seems to load the right vm >>> >>> * ./pharo-ui Pharo.image >>> >>> Starts the vm but complains about : >>> "Pharo cannot write to the changes file named >>> u:\tmp\pharo\Pharo.changes." >>> >>> I am sure the file is writable. >>> >>> The vm reports to be built on aug 27 2017, is this right? >>> >>> >>> I think is this one: >>> >>> https://pharo.fogbugz.com/f/cases/20805/Cannot-write-to-the- >>> changes-file-error-on-Windows >>> >>> >>> yes, this is a known bug that we need to fix soon. >>> >>> Setting up Iceberg: >>> Yes, need option 2, that is, I use the commandline to clone a repository >>> and >>> add it to iceberg. Cloning from iceberg directly does not work (long file >>> names). >>> >>> >>> that should not be anymore an issue (since we migrated to tonel). >>> but cloning in disk is faster :) >>> >>> Ok, >>> now I see some uncommitted changes, the guide says: "you may need to >>> invoke >>> synchronize" >>> >>> But how? >>> There is a "synchronize repository... " and "Synchronize full repository >>> ..." >>> menu entry. >>> >>> Which one? >>> The first synchronize does not show me how to actually do anything >>> and the second one shows a intimidating warning :) >>> FInally I removed my fork (it was pretty old), did a new fork and >>> sstarted >>> with >>> a fresh image. >>> >>> >>> I fixed thatâ¦ it should be the first synchronize. But you do not have to >>> do anything other than execute it ;) >>> anyway, what I need to do is to put a note of what happens if (as you) >>> your fork is too old: in that case you can go to Pharo/Synchronize >>> repositories (but anyway, you do not need itâ¦ creating a branch from >>> fogbugz issue will do a fetch and put you in the right place). >>> >>> >>> >>> Finally, the initial setup up is done, I now try to do some work with it >>> and report back >>> >>> >>> thanks! >>> I hope everything goes smooth :) >>> >> >> Not that smooth. The view for pull requests is still problematic, it >> seems to do alot in the background on >> resizing the window (it is slow, does it do some lgit-calls on every >> window change ?) . >> And it crashes often. >> >> [image: Inline-Bild 1] >> >> >>> >>> cheers! >>> Esteban >>> >>> >>> >>> nicolai >>> >>> >>> >>> >> >

Feb. 4, 2018

Re: [Pharo-dev] Feedback about "Contribute a Fix to Pharo" (For windows users)

by Nicolai Hess

And sometimes I get a debugger: [image: Inline-Bild 1] And btw, the diff pane "Left: working copy / Right: incoming updates" This is wrong, the working copy is on the right, no ? 2018-02-04 2:12 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > > > 2018-02-03 19:54 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> >> >> On 3 Feb 2018, at 17:09, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> >> wrote: >> >> Hi Nicolai, >> >> 2018-02-03 10:42 GMT-03:00 Nicolai Hess <nicolaihess(a)gmail.com>: >> >> The setup finally somehow works: >> >> I followed the guide at >> https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo >> >> * wget -O- get.pharo.org/70+vm | bash >> >> >> Does not work (windows msys-console) >> It starts donwloading something but not pharo >> >> >> this is very weird, I will check. >> >> >> I tried to do at seperate steps: >> Only the image >> * wget -O- get.pharo.org/70 | bash >> >> Works >> >> * wget -O- get.pharo.org/vm | bash >> >> works, but is the wrong VM I guess, I can not open the image >> >> * wget -O- get.pharo.org/vm70 | bash >> >> works, seems to load the right vm >> >> * ./pharo-ui Pharo.image >> >> Starts the vm but complains about : >> "Pharo cannot write to the changes file named u:\tmp\pharo\Pharo.changes." >> >> I am sure the file is writable. >> >> The vm reports to be built on aug 27 2017, is this right? >> >> >> I think is this one: >> >> https://pharo.fogbugz.com/f/cases/20805/Cannot-write-to-the- >> changes-file-error-on-Windows >> >> >> yes, this is a known bug that we need to fix soon. >> >> Setting up Iceberg: >> Yes, need option 2, that is, I use the commandline to clone a repository >> and >> add it to iceberg. Cloning from iceberg directly does not work (long file >> names). >> >> >> that should not be anymore an issue (since we migrated to tonel). >> but cloning in disk is faster :) >> >> Ok, >> now I see some uncommitted changes, the guide says: "you may need to >> invoke >> synchronize" >> >> But how? >> There is a "synchronize repository... " and "Synchronize full repository >> ..." >> menu entry. >> >> Which one? >> The first synchronize does not show me how to actually do anything >> and the second one shows a intimidating warning :) >> FInally I removed my fork (it was pretty old), did a new fork and sstarted >> with >> a fresh image. >> >> >> I fixed thatâ¦ it should be the first synchronize. But you do not have to >> do anything other than execute it ;) >> anyway, what I need to do is to put a note of what happens if (as you) >> your fork is too old: in that case you can go to Pharo/Synchronize >> repositories (but anyway, you do not need itâ¦ creating a branch from >> fogbugz issue will do a fetch and put you in the right place). >> >> >> >> Finally, the initial setup up is done, I now try to do some work with it >> and report back >> >> >> thanks! >> I hope everything goes smooth :) >> > > Not that smooth. The view for pull requests is still problematic, it seems > to do alot in the background on > resizing the window (it is slow, does it do some lgit-calls on every > window change ?) . > And it crashes often. > > [image: Inline-Bild 1] > > >> >> cheers! >> Esteban >> >> >> >> nicolai >> >> >> >> >

Feb. 4, 2018