October 2017 - Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #245: 18391-Debugger must guard against actions on process termination

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

There is a new Pharo build available! The status of the build #245 was: SUCCESS. The Pull Request #409 was integrated: "18391-Debugger must guard against actions on process termination" Pull request url: https://github.com/pharo-project/pharo/pull/409 Issue Url: https://pharo.fogbugz.com/f/cases/development Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 31, 2017

[Iceberg] Couple of bugs/problems on Iceberg

by Mariano Martinez Peck

Hi guys, 1) I am reviewing an awesome PR from Guille and I think the labels "Left: working copy" and "Right: incoming updates" are switched. Look at the attached screenshot. In this example, the method `waitForExitWithTimeout:` is new and comes from the update (PR), its NOT not on my working copy. 2) Subtree revert not possible? Let's say I have a class with 2 methods I changed and I want to revert both. I thought that reverting the class would do the trick and revert all the inner tree. But no, I am getting a `nil dnu #inverse`. Look at the attached screenshot. I mean to revert OSUnixSubprocess (hence, both methods below). 3) The scrolling of versions in the PR review feels slow... and my project is tiny... is that using "FastTable" ? Btw...I would also love if upper and down keys could be used in that table. Thanks in advance, -- Mariano http://marianopeck.wordpress.com

Oct. 31, 2017

[Pharo 7.0-dev] Build #244: 20581-Manually-resolved-dependencies-in-manifests-need-update

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

There is a new Pharo build available! The status of the build #244 was: SUCCESS. The Pull Request #391 was integrated: "20581-Manually-resolved-dependencies-in-manifests-need-update" Pull request url: https://github.com/pharo-project/pharo/pull/391 Issue Url: https://pharo.fogbugz.com/f/cases/20581 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 31, 2017

Re: [Pharo-dev] [IMPORTANT] STOP THE WORLD: Please do not contribute today, we are going to migrate to tonel

by Tudor Girba

+100! Doru > On Oct 31, 2017, at 11:50 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Tx guys! > > > On Tue, Oct 31, 2017 at 11:09 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> Hi, >> >> Subject says pretty much all: we are going to handle the migration to Tonel >> today. >> It will be more or less like this: >> >> - we will merge all mergable pull requests. >> - we will close not-mergable ones and we will ask to re-submit with new >> format later. >> - we will do a PR with the conversion (issue is >> https://pharo.fogbugz.com/f/cases/20616) >> - we will make it work and pass tests :) >> - we will merge >> >> IMPORTANT: After conversion is done, you will need to download a new Pharo >> 7.0a. >> IMPORTANT2: We will publish a review of the contribution process soon too. >> >> Esteban > -- www.tudorgirba.com www.feenk.com "Every now and then stop and ask yourself if the war you're fighting is the right one."

Oct. 31, 2017

[Pharo 7.0-dev] Build #243: 20584-SortFunction-should-not-use-block-in-collator

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

There is a new Pharo build available! The status of the build #243 was: SUCCESS. The Pull Request #412 was integrated: "20584-SortFunction-should-not-use-block-in-collator" Pull request url: https://github.com/pharo-project/pharo/pull/412 Issue Url: https://pharo.fogbugz.com/f/cases/20584 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 31, 2017

Re: [Pharo-dev] Stuck trying to contribute

by Sven Van Caekenberghe

> On 31 Oct 2017, at 11:52, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Sven > > have a look at the TipsAndTricks new booklet available at http://books.pharo.org. There is a configuration for iceberg that sets and reduce > the pain for me. Ah, OK, found it. Thanks. Nice document BTW ;-) > Stef > > > On Tue, Oct 31, 2017 at 10:51 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > >> On 31 Oct 2017, at 10:37, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >> >> If you give me precise instructions I can update the post :) > > precise instructions is: > - do not use https, use ssh > - if you do not follow our recommendation and you insist on use https, add your credentials before doing any commit. > >> >> On Mon, Oct 30, 2017 at 10:03 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> I think I succeeded: >> >> https://pharo.fogbugz.com/f/cases/20613/Improve-some-UUID-comments >> https://github.com/pharo-project/pharo/pull/420 >> >> It does contain 4 identical commits due to my troubles earlier on. >> I also did not see a confirmation by way of an #inform: after the pull request in Iceberg. >> >> > On 30 Oct 2017, at 21:50, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> > >> > >> > >> >> On 30 Oct 2017, at 21:42, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> >> >> hi, >> >> >> >> thing is, you should not use https authentication (and the guide should not point to it) >> >> Using SSH mode works out of the box. >> >> Using HTTPS there is currently a bug and the workaround is to introduce your credentials *before* trying to commit (in settings) >> > >> > Well, after entering my username/password in Settings > Tools > Software Configuration Management > Iceberg > Plaintext Credentials I am one step further - I managed to 'Commit & Push'. >> > >> > Thanks ! >> > >> >> Esteban >> >> >> >>> On 30 Oct 2017, at 20:33, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> >> >>> Hi, >> >>> >> >>> Sorry, but I am person 237 trying to contribute to Pharo 7 the new way. >> >>> >> >>> I was following https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to… and I got stuck just before step 3, after trying to do "That will calculate the differences between the checked-out branch and your image, show you the tree with the differences and let you commit (and push)". Specifically, the 'and push' fails. >> >>> >> >>> $ sw_vers >> >>> ProductName: Mac OS X >> >>> ProductVersion: 10.13 >> >>> BuildVersion: 17A405 >> >>> >> >>> $ curl get.pharo.org/70+vm | bash >> >>> ... >> >>> >> >>> $ ./pharo-ui Pharo.image >> >>> >> >>> I now have the following setup, which is correct I think. >> >>> >> >>> <Screen Shot 2017-10-30 at 20.28.05.png> >> >>> >> >>> I can commit on my local branch (left button), but when I try to do the 'and Push' (right button), things hang after I enter my credentials. >> >>> >> >>> Locally, I see >> >>> >> >>> $ git status >> >>> On branch 20613-Improve-some-UUID-comments >> >>> nothing to commit, working tree clean >> >>> >> >>> with the new code already committed >> >>> >> >>> $ cat src/Network-UUID.package/UUID.class/class/new.st >> >>> instance creation >> >>> new >> >>> "Create and return a new UUID" >> >>> >> >>> "self new" >> >>> >> >>> ^ (self new: 16) >> >>> >> >>> What did I do wrong ? How do I proceed ? >> >>> >> >>> Sven >> >>> >> >> >> > >> >> >> >> >> >> -- >> >> 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 >> >> Web: http://guillep.github.io >> Phone: +33 06 52 70 66 13 > >

Oct. 31, 2017

Re: [Pharo-dev] Stuck trying to contribute

by Stephane Ducasse

Sven have a look at the TipsAndTricks new booklet available at http://books.pharo.org. There is a configuration for iceberg that sets and reduce the pain for me. Stef On Tue, Oct 31, 2017 at 10:51 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > On 31 Oct 2017, at 10:37, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > If you give me precise instructions I can update the post :) > > > precise instructions is: > - do not use https, use ssh > - if you do not follow our recommendation and you insist on use https, add > your credentials before doing any commit. > > > On Mon, Oct 30, 2017 at 10:03 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > >> I think I succeeded: >> >> https://pharo.fogbugz.com/f/cases/20613/Improve-some-UUID-comments >> https://github.com/pharo-project/pharo/pull/420 >> >> It does contain 4 identical commits due to my troubles earlier on. >> I also did not see a confirmation by way of an #inform: after the pull >> request in Iceberg. >> >> > On 30 Oct 2017, at 21:50, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> > >> > >> > >> >> On 30 Oct 2017, at 21:42, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> >> >> >> hi, >> >> >> >> thing is, you should not use https authentication (and the guide >> should not point to it) >> >> Using SSH mode works out of the box. >> >> Using HTTPS there is currently a bug and the workaround is to >> introduce your credentials *before* trying to commit (in settings) >> > >> > Well, after entering my username/password in Settings > Tools > >> Software Configuration Management > Iceberg > Plaintext Credentials I am >> one step further - I managed to 'Commit & Push'. >> > >> > Thanks ! >> > >> >> Esteban >> >> >> >>> On 30 Oct 2017, at 20:33, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> >> >>> Hi, >> >>> >> >>> Sorry, but I am person 237 trying to contribute to Pharo 7 the new >> way. >> >>> >> >>> I was following https://github.com/guillep/Pha >> roIntegrationProcess/wiki/Contribute-a-fix-to-Pharo and I got stuck just >> before step 3, after trying to do "That will calculate the differences >> between the checked-out branch and your image, show you the tree with the >> differences and let you commit (and push)". Specifically, the 'and push' >> fails. >> >>> >> >>> $ sw_vers >> >>> ProductName: Mac OS X >> >>> ProductVersion: 10.13 >> >>> BuildVersion: 17A405 >> >>> >> >>> $ curl get.pharo.org/70+vm | bash >> >>> ... >> >>> >> >>> $ ./pharo-ui Pharo.image >> >>> >> >>> I now have the following setup, which is correct I think. >> >>> >> >>> <Screen Shot 2017-10-30 at 20.28.05.png> >> >>> >> >>> I can commit on my local branch (left button), but when I try to do >> the 'and Push' (right button), things hang after I enter my credentials. >> >>> >> >>> Locally, I see >> >>> >> >>> $ git status >> >>> On branch 20613-Improve-some-UUID-comments >> >>> nothing to commit, working tree clean >> >>> >> >>> with the new code already committed >> >>> >> >>> $ cat src/Network-UUID.package/UUID.class/class/new.st >> >>> instance creation >> >>> new >> >>> "Create and return a new UUID" >> >>> >> >>> "self new" >> >>> >> >>> ^ (self new: 16) >> >>> >> >>> What did I do wrong ? How do I proceed ? >> >>> >> >>> Sven >> >>> >> >> >> > >> >> >> > > > -- > > 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 <+33%206%2052%2070%2066%2013> > > >

Oct. 31, 2017

Re: [Pharo-dev] [IMPORTANT] STOP THE WORLD: Please do not contribute today, we are going to migrate to tonel

by Stephane Ducasse

Tx guys! On Tue, Oct 31, 2017 at 11:09 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > Subject says pretty much all: we are going to handle the migration to Tonel > today. > It will be more or less like this: > > - we will merge all mergable pull requests. > - we will close not-mergable ones and we will ask to re-submit with new > format later. > - we will do a PR with the conversion (issue is > https://pharo.fogbugz.com/f/cases/20616) > - we will make it work and pass tests :) > - we will merge > > IMPORTANT: After conversion is done, you will need to download a new Pharo > 7.0a. > IMPORTANT2: We will publish a review of the contribution process soon too. > > Esteban

Oct. 31, 2017

[IMPORTANT] STOP THE WORLD: Please do not contribute today, we are going to migrate to tonel

by Esteban Lorenzano

Hi, Subject says pretty much all: we are going to handle the migration to Tonel today. It will be more or less like this: - we will merge all mergable pull requests. - we will close not-mergable ones and we will ask to re-submit with new format later. - we will do a PR with the conversion (issue is https://pharo.fogbugz.com/f/cases/20616 <https://pharo.fogbugz.com/f/cases/20616>). - we will make it work and pass tests :) - we will merge IMPORTANT: After conversion is done, you will need to download a new Pharo 7.0a. IMPORTANT2: We will publish a review of the contribution process soon too. Esteban

Oct. 31, 2017

[Pharo 7.0-dev] Build #242: 20602 file locator local directory should be inside image directory

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

There is a new Pharo build available! The status of the build #242 was: SUCCESS. The Pull Request #419 was integrated: "20602 file locator local directory should be inside image directory" Pull request url: https://github.com/pharo-project/pharo/pull/419 Issue Url: https://pharo.fogbugz.com/f/cases/20602 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 31, 2017