- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #439: Improve Athens-Cairo-Tests
by ci-pharo-ci-jenkins2＠inria.fr July 5, 2019

July 5, 2019

There is a new Pharo build available! The status of the build #439 was: FAILURE. The Pull Request #3793 was integrated: "Improve Athens-Cairo-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/3793 Issue Url: https://github.com/pharo-project/pharo/issues/3791 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #438: Remove unnecessary temps in RBScannerTest test methods
by ci-pharo-ci-jenkins2＠inria.fr July 5, 2019

July 5, 2019

There is a new Pharo build available! The status of the build #438 was: FAILURE. The Pull Request #3790 was integrated: "Remove unnecessary temps in RBScannerTest test methods" Pull request url: https://github.com/pharo-project/pharo/pull/3790 Issue Url: https://github.com/pharo-project/pharo/issues/3788 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #437: RBParseTreeTests should be abstract test class
by ci-pharo-ci-jenkins2＠inria.fr July 5, 2019

July 5, 2019

There is a new Pharo build available! The status of the build #437 was: SUCCESS. The Pull Request #3789 was integrated: "RBParseTreeTests should be abstract test class" Pull request url: https://github.com/pharo-project/pharo/pull/3789 Issue Url: https://github.com/pharo-project/pharo/issues/3787 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #436: Cleanup EdgeGripMorph
by ci-pharo-ci-jenkins2＠inria.fr July 5, 2019

July 5, 2019

There is a new Pharo build available! The status of the build #436 was: FAILURE. The Pull Request #3778 was integrated: "Cleanup EdgeGripMorph" Pull request url: https://github.com/pharo-project/pharo/pull/3778 Issue Url: https://github.com/pharo-project/pharo/issues/3777 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #435: 3761-CompiledCodeargumentNames-should-be-reviewed
by ci-pharo-ci-jenkins2＠inria.fr July 5, 2019

July 5, 2019

There is a new Pharo build available! The status of the build #435 was: SUCCESS. The Pull Request #3762 was integrated: "3761-CompiledCodeargumentNames-should-be-reviewed" Pull request url: https://github.com/pharo-project/pharo/pull/3762 Issue Url: https://github.com/pharo-project/pharo/issues/3761 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #434: Cleanups in GT-Tests-Inspector
by ci-pharo-ci-jenkins2＠inria.fr July 5, 2019

July 5, 2019

There is a new Pharo build available! The status of the build #434 was: SUCCESS. The Pull Request #3770 was integrated: "Cleanups in GT-Tests-Inspector" Pull request url: https://github.com/pharo-project/pharo/pull/3770 Issue Url: https://github.com/pharo-project/pharo/issues/3769 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #433: Lint fix for readEvalPrint
by ci-pharo-ci-jenkins2＠inria.fr July 5, 2019

July 5, 2019

There is a new Pharo build available! The status of the build #433 was: SUCCESS. The Pull Request #3768 was integrated: "Lint fix for readEvalPrint" Pull request url: https://github.com/pharo-project/pharo/pull/3768 Issue Url: https://github.com/pharo-project/pharo/issues/3767 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #432: Typo: explicitely should be explicitly
by ci-pharo-ci-jenkins2＠inria.fr July 5, 2019

July 5, 2019

There is a new Pharo build available! The status of the build #432 was: SUCCESS. The Pull Request #3766 was integrated: "Typo: explicitely should be explicitly" Pull request url: https://github.com/pharo-project/pharo/pull/3766 Issue Url: https://github.com/pharo-project/pharo/issues/3765 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Additional Divider in Pharo menu
by Torsten Bergmann July 5, 2019

July 5, 2019

Hi, around 20 days ago the order of menu items in the Pharo world menu were munged up in the standard Pharo 8 image for whatever reasons. "Safe" was on first position and not grouped with other "Save ..." items anymore as it was in the past. This was noted by Alexandre Bergel and others on Discord. I fixed the order in the following PULL REQUEST https://github.com/pharo-project/pharo/pull/3529 with the menu ending up looking like this: !-------------------- ! SETTINGS !-------------------- ! SAVE ! SAVE AS ! SAVE AND QUIT !-------------------- ! QUIT !-------------------- having added by intention an additional divider between - the more safe options to store the image (secure) - the unsafe quit where one can loose changes in the image (insecure if you just quit) I know that "SAVE AND QUIT" and "QUIT" also might belong somehow together as both exit the image - but the diver should separate the more secure options from the more insecure options. Now today the divider was removed again using https://github.com/pharo-project/pharo/pull/3738 from Cyril Ferlicot mentioning it as "unwanted" - so now the menu looks like this: !-------------------- ! SETTINGS !-------------------- ! SAVE ! SAVE AS ! SAVE AND QUIT ! QUIT !-------------------- as it was back in Pharo 7. As I'm someone who is mousing around very quickly in the past it often happened to me that while I wanted to really "SAVE AND QUIT" I hit accidentally the "QUIT" button directly below - leaving me in a state where I had to recover or reapplying changes afterwards. So using the additonal divider between the three "safe my data" options and the "just leave" was intentional and to me makes some sense: from the point of view of grouping, visually and from clicking behavior. I guess Cyril Ferlicot wanted to restore how it looked in Pharo 7 or had other reasons why he prefers the menu to look like in the second picture. I know it is not a big thing - but nonetheless: It would be good if others could write which option a) WITH DIVIDER (as in first picture to separate safe from unsafe options) or b) WITHOUT DIVIDER (as in second picture to stay like it was back in Pharo 7) they really prefer so we can decide on a community / voters base. Thx and sorry for the ASCII art T.

4 4

Iceberg > trouble creating branches
by Ben Coman July 5, 2019

July 5, 2019

In latest Pharo 8.0 (2019-07-05)(55f0b29) in Iceberg going Pharo > Create new branch from Issue is not picking up Issues from Github, only from Fogbugz. I'm half-sure that its been working for Github Issues ?? Then also Repository > Branch button is reporting an error with DropListPresenter "NotFound: selectedItem ..." called from IceTipSelectRemotePresenter >> initializeWidgets I guess some of this is the in-progress Spec2 updates. For others, I found a working option with Packages > Branch button. cheers -ben

1 0