- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #601: 4214-Code-Completion-DNU-on-visitAssignmentNode
by ci-pharo-ci-jenkins2＠inria.fr Aug. 6, 2019

Aug. 6, 2019

There is a new Pharo build available! The status of the build #601 was: FAILURE. The Pull Request #4215 was integrated: "4214-Code-Completion-DNU-on-visitAssignmentNode" Pull request url: https://github.com/pharo-project/pharo/pull/4215 Issue Url: https://github.com/pharo-project/pharo/issues/4214 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Iceberg and package renamings
by Torsten Bergmann Aug. 6, 2019

Aug. 6, 2019

Hi, usually when contributing I download a fresh Pharo 8 image (built by CI) using either Launcher or ZeroConf and use the Iceberg "repair" functionality to connect to / checkout the existing local clone of the repo with the Pharo 8 branch. This way I usually easily come easily to the "up to date" state and can start own modifications. But this time I used an older Pharo 8 image. So I pulled from upstream, pushed to my origin (forked git repo) and updated an already existing image also using the "repair" functionality. The changes where assembled and loaded. This way I also got into the "up to date" state for this image. But as one of the last changes done was a package renaming of "ReleaseTest" into "Release-Tests" this was reflected on the "src" folder on disk but not in the image itself. So unfortunately - the git repo was already having a "Release-Tests" folder in synch with the upstream - the local "up to date" image stayed with the old "ReleaseTests" package name as it was updated and not freshly bootstrapped from Baselines and with this out of synch. See attached screenshot. So I guess Iceberg's updating can not yet properly handle package renamings, maybe this is a known bug / not yet implemented feature - or something that is not easy to fix due to the renaming. Is this known? Could it be handled in the future? Just want to mention this as this could be a source of further problems when contributors update their image instead of using a new CI built one as they may hit such a renamed package. Bye T.

1 0

[Pharo 8.0] Build #600: Remove-shadow-variables
by ci-pharo-ci-jenkins2＠inria.fr Aug. 6, 2019

Aug. 6, 2019

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

1 0

[Pharo 8.0] Build #599: 4206-Cleaning-arcTan-comment-and-adding-executable-comments
by ci-pharo-ci-jenkins2＠inria.fr Aug. 6, 2019

Aug. 6, 2019

There is a new Pharo build available! The status of the build #599 was: SUCCESS. The Pull Request #4207 was integrated: "4206-Cleaning-arcTan-comment-and-adding-executable-comments" Pull request url: https://github.com/pharo-project/pharo/pull/4207 Issue Url: https://github.com/pharo-project/pharo/issues/4206 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #598: Move method to make it work
by ci-pharo-ci-jenkins2＠inria.fr Aug. 6, 2019

Aug. 6, 2019

There is a new Pharo build available! The status of the build #598 was: FAILURE. The Pull Request #4202 was integrated: "Move method to make it work" Pull request url: https://github.com/pharo-project/pharo/pull/4202 Issue Url: https://github.com/pharo-project/pharo/issues/fix/udptest Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #597: Fixing the dependency analysis of BaselineOfIDE
by ci-pharo-ci-jenkins2＠inria.fr Aug. 6, 2019

Aug. 6, 2019

There is a new Pharo build available! The status of the build #597 was: SUCCESS. The Pull Request #4200 was integrated: "Fixing the dependency analysis of BaselineOfIDE" Pull request url: https://github.com/pharo-project/pharo/pull/4200 Issue Url: https://github.com/pharo-project/pharo/issues/fixing Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[FileReference] why this class don't provide a method isAHiddenFile ?
by ClÃ©ment Dutriez Aug. 6, 2019

Aug. 6, 2019

-- Dutriez ClÃ©ment dutriezcle(a)gmail.com 0605199489 [image: www.linkedin.com/in/clÃ©ment-dutriez-407275173] <http://www.linkedin.com/in/clÃ©ment-dutriez-407275173>

4 9

[ANN] Pharo Launcher 1.9.1 released
by Christophe Demarey Aug. 6, 2019

Aug. 6, 2019

Hi all, We are pleased to announce Pharo Launcher 1.9.1 release! The goal of this release is to have a better Windows support. Indeed Pharo Launcher now uses a new library OSWinSubprocess (https://github.com/pharo-contributions/OSWinSubprocess <https://github.com/pharo-contributions/OSWinSubprocess>) created for Pharo Launcher needs. This library allows to create Windows processes through ffi calls to the Windows API. It uses the unicode api, allowing paths with non-ascii characters. In the same time, we switched from OSProcess to OSSubprocess (Linux and OS X) that is now the preferred library to use to fork processes on Linux-based systems. This release is not yet the default download of Pharo Launcher on Pharo web site because we want more feedback before promoting it. Please use this link to install it: https://files.pharo.org/pharo-launcher/1.9 <https://files.pharo.org/pharo-launcher/1.9> and let us know if this version works fine/better for you. ps: For now, the binary is not signed but it will come soon. ps2: Thanks to Keldon Alleyne for his PR on Pharo Launcher offering the first FFI binding to Windows process API Regards, The Pharo team.

4 9

Two Surprising and Scary FS Behaviors
by Sean P. DeNigris Aug. 6, 2019

Aug. 6, 2019

I may be ignorant of some key principle in the filesystem world, but IMHO conceptually, `location / somethingElse` should always return either location or something inside of it, unless the request explicitly requests otherwise (e.g. location / '..'). To do otherwise could be disastrous. Behavior #1 rootDataFolder := FileLocator home / 'a' / 'b' / . subfolderName := self accidentallyReturnAnEmptyString. assumedToBeInRootData := rootDataFolder / subfolderName. assumedToBeInRootData deleteAll. "I hope I have a recent machine backup, because..." assumedToBeInRootData resolve = FileLocator root resolve. "WTH?!" Behavior 2 (similar) Path * 'a' / 'b' / '/' = Path root. "WTH?!" ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 1

[Pharo 8.0] Build #596: 4137-Code-completion-error
by ci-pharo-ci-jenkins2＠inria.fr Aug. 5, 2019

Aug. 5, 2019

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

1 0