- Pharo-dev - lists.pharo.org

Esteban's ChangeLog week of 17 September 2018
by estebanlm＠gmail.com Sept. 27, 2018

Sept. 27, 2018

Hello! This is my weekly ChangeLog, from 17 September 2018 to 23 September 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=17/9/2018&to=23/9/2018 ChangeLog ========= 19 September 2018: ------------------ * I migrated all [pharo-ide](https://github.com/pharo-ide) projects to tonel format. Harder than it seems, it took me a good bunch of hours. But now is working. This will enhance work/fixes on Calypso. 18 September 2018: ------------------ * I just [fixed the CI for Calypso](https://github.com/pharo-ide/Calypso/issues/319) (it was failing for Pharo 7.0 because of problems when updating). Now I can start fixing real issues of it :) 17 September 2018: ------------------ * I backported/promoted a new stable vm for Pharo 6.1. This is the one that has been tested for Pharo 7.0alpha already for some time, so things should be fine. Current stable VM is from 2018-07-04 (yeah, eventually we will have a decent semver numbering, but for now this will have to be enough :P) cheers! Esteban

3 3

Top MenuBar does not auto follow font changes
by Sven Van Caekenberghe Sept. 27, 2018

Sept. 27, 2018

Hi, The Top MenuBar does not seem to auto follow font changes, although it picks them uppitiest when you hide/show the menu bar from the Settings. Sven

1 0

[Pharo 7.0-dev] Build #1272: 22490-It-seems-that-openFileStreamwritable-is-dead-code
by ci-pharo-ci-jenkins2＠inria.fr Sept. 27, 2018

Sept. 27, 2018

There is a new Pharo build available! The status of the build #1272 was: SUCCESS. The Pull Request #1827 was integrated: "22490-It-seems-that-openFileStreamwritable-is-dead-code" Pull request url: https://github.com/pharo-project/pharo/pull/1827 Issue Url: https://pharo.fogbugz.com/f/cases/22490 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] [Pharo 7.0-dev] Build #1271: 22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary
by Esteban Lorenzano Sept. 26, 2018

Sept. 26, 2018

> On 26 Sep 2018, at 15:24, Petr Fischer via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Petr Fischer <petr.fischer(a)me.com> > Subject: Re: [Pharo-dev] [Pharo 7.0-dev] Build #1271: 22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary > Date: 26 September 2018 at 15:24:49 CEST > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > > Hello, why is test status of this pull request: FAILURE? > > Thanks for clarification, Petr Fischer Is a misleading message. It means merge was done, but for some reason (usually network problems), some tests failed to run. We are working on fix that (but you knowâ¦ time :P). Esteban > > >> There is a new Pharo build available! >> >> The status of the build #1271 was: FAILURE. >> >> The Pull Request #1823 was integrated: "22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary" >> Pull request url: https://github.com/pharo-project/pharo/pull/1823 >> >> Issue Url: https://pharo.fogbugz.com/f/cases/22483 >> Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… > > > >

1 0

Re: [Pharo-dev] [Pharo 7.0-dev] Build #1271: 22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary
by Marcus Denker Sept. 26, 2018

Sept. 26, 2018

Hi, It means that the build for this one merge failedâ¦ build got much more stable over the last weeks, but we still sometimes have crashes (here it seems to be the text render bug) But this is undefended of the merge: the next build then will take this into account. > On 26 Sep 2018, at 15:24, Petr Fischer via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Petr Fischer <petr.fischer(a)me.com> > Subject: Re: [Pharo-dev] [Pharo 7.0-dev] Build #1271: 22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary > Date: 26 September 2018 at 15:24:49 CEST > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > > Hello, why is test status of this pull request: FAILURE? > > Thanks for clarification, Petr Fischer > > >> There is a new Pharo build available! >> >> The status of the build #1271 was: FAILURE. >> >> The Pull Request #1823 was integrated: "22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary" >> Pull request url: https://github.com/pharo-project/pharo/pull/1823 >> >> Issue Url: https://pharo.fogbugz.com/f/cases/22483 >> Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… > > > >

1 0

[Pharo 7.0-dev] Build #1271: 22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary
by ci-pharo-ci-jenkins2＠inria.fr Sept. 26, 2018

Sept. 26, 2018

There is a new Pharo build available! The status of the build #1271 was: FAILURE. The Pull Request #1823 was integrated: "22483-CollectiongroupedBy---preserve-key-order-in-final-grouped-dictionary" Pull request url: https://github.com/pharo-project/pharo/pull/1823 Issue Url: https://pharo.fogbugz.com/f/cases/22483 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

2 1

[Pharo 7.0-dev] Build #1270: 22221-Jump-to-next-keyword
by ci-pharo-ci-jenkins2＠inria.fr Sept. 26, 2018

Sept. 26, 2018

There is a new Pharo build available! The status of the build #1270 was: SUCCESS. The Pull Request #1722 was integrated: "22221-Jump-to-next-keyword" Pull request url: https://github.com/pharo-project/pharo/pull/1722 Issue Url: https://pharo.fogbugz.com/f/cases/jump Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1269: 22481-NetNameResolver-classlocalHostAddress---error-check-with-default
by ci-pharo-ci-jenkins2＠inria.fr Sept. 26, 2018

Sept. 26, 2018

There is a new Pharo build available! The status of the build #1269 was: FAILURE. The Pull Request #1822 was integrated: "22481-NetNameResolver-classlocalHostAddress---error-check-with-default" Pull request url: https://github.com/pharo-project/pharo/pull/1822 Issue Url: https://pharo.fogbugz.com/f/cases/22481 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

IoT hackathon @zweidenker
by Norbert Hartl Sept. 26, 2018

Sept. 26, 2018

Hi, we (ZWEIDENKER) and RModD organized an IoT Hackathon in cologne at 19th of october 2018. The plan will be: - Allex Oliviera will present the tutorial he made on PharoThings [1]. The audience will try it in a hands-on-session and give feedback to improve it. Zweidenker is sponsoring the hardware so nobody has to bring anything to the session - We are collecting ideas at the moment what we want to do with the learnings from Allex, meaning what hardware to build - If you have ideas about what to build with real life things that should be connected from pharo, please tell us. We will compile a list of ideas and for the first two or three we will buy the necessary hardware so we can build it at that day The Hackathon will take place at ZWEIDENKER GmbH Luxemburger Str. 72 50674 KÃ¶ln germany As we have a limited amount of seats you need to register if you are interested. Go to http://zweidenker.de/en/iot-hackathon-2018 <http://zweidenker.de/en/iot-hackathon-2018> to register your seat on the session. If there are more participants than seats we will have to do selection by dice rolling. Registration period ends on 5th of october so you will know in advance if you can come. See you there, Norbert on behalf of ZWEIDENKER [1] https://github.com/pharo-iot/PharoThings <https://github.com/pharo-iot/PharoThings>

1 0

[Pharo 7.0-dev] Build #1268: 22488-Bootstrapping-from-outside-of-the-repository-broken
by ci-pharo-ci-jenkins2＠inria.fr Sept. 26, 2018

Sept. 26, 2018

There is a new Pharo build available! The status of the build #1268 was: SUCCESS. The Pull Request #1826 was integrated: "22488-Bootstrapping-from-outside-of-the-repository-broken" Pull request url: https://github.com/pharo-project/pharo/pull/1826 Issue Url: https://pharo.fogbugz.com/f/cases/22488 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0