January 2019 - Pharo-dev - lists.pharo.org

Better management of encoding of environment variables
by Guillermo Polito Jan. 22, 2019

Jan. 22, 2019

Hi all, following the meeting we had here @Inria headquarters, I'll be backporting some of the improvements we did in the launcher this last month regarding the encoding of environment variables. I've opened for this issue https://pharo.fogbugz.com/f/cases/22658/ We have already studied possible alternatives with Pablo and Christophe and we have some conclusions and we propose some changes: API Proposal for OSEnvironment ========================= - *at: aVariableName * Gets the String value of an environment variable called `aVariableName` It is the system reponsibility to manage the encoding. Rationale: A common denominator for all platforms providing an already decoded string, because windows does not (compared to *nix systems) provide a encoded byte representation of the value. Windows has instead its own wide string representation. - *[optionally] rawAt: anEncodedVariableName* Gets the Byte value of an environment variable called `anEncodedVariableName`. It is the user responsibility to encode and decode argument and return values in the encoding of this preference. Rationale: Some systems may want to have the liberty to use different encodings, or even to put binary data in the variables. - *[optionally] at: aVariableName encoding: anEncoding* Gets the value of an environment variable called `aVariableName` using `anEncoding` to encode/decode arguments and return values. Rationale: *xes could potentially use different encodings for their environment variables or even use different encodings in different parts of their file system. Other Implementation details ========================= - VM primitives returning paths Strings should be carefuly managed to decode them, since they are actually C strings (so byte arrays) disguised as ByteStrings. - Windows requires calling the right *Wide version of the functions from C, plus the correct encoding routine. This could be implemented as an FFI call or by modifying the VM to do it properly instead of calling the Ascii version

9 23

[Pharo 7.0] Build #142: 22901-Image-crash-on-commit-and-push-in-windows-64bit
by ci-pharo-ci-jenkins2＠inria.fr Jan. 22, 2019

Jan. 22, 2019

There is a new Pharo build available! The status of the build #142 was: SUCCESS. The Pull Request #2295 was integrated: "22901-Image-crash-on-commit-and-push-in-windows-64bit" Pull request url: https://github.com/pharo-project/pharo/pull/2295 Issue Url: https://pharo.fogbugz.com/f/cases/22901 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #141: 22901-Image-crash-on-commit-and-push-in-windows-64bit
by ci-pharo-ci-jenkins2＠inria.fr Jan. 22, 2019

Jan. 22, 2019

There is a new Pharo build available! The status of the build #141 was: SUCCESS. The Pull Request #2295 was integrated: "22901-Image-crash-on-commit-and-push-in-windows-64bit" Pull request url: https://github.com/pharo-project/pharo/pull/2295 Issue Url: https://pharo.fogbugz.com/f/cases/22901 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Pharo 6.1 backport
by Gabriel Cotelli Jan. 22, 2019

Jan. 22, 2019

Hi! Now that release madness is over ;) can we get https://pharo.manuscript.com/f/cases/22869/Backport-fix-of-MetacelloCypress… merged? I'm holding back some releases waiting for this change to not break Pharo 6.1 support. Thank you!

2 1

[ANN] Pharo 8.0 development started!
by Esteban Lorenzano Jan. 22, 2019

Jan. 22, 2019

Hi, As you know, after releasing a version of Pharo, a new cycle of development starts. There is no perfect release, and with Pharo we play an infinite game (see Marcus talk at ESUG). So, now Pharo 7.0 has entered maintenance mode and Pharo 8.0 is the new development branch. That means: - Pharo 7.0 will have critical bugfix releases. - But since bugs will happen and improving is a constant work, most bugfixes will happen in Pharo 8.0. Let the fun continue! Esteban

1 0

[Pharo 7.0] Build #140: SUCCESS
by ci-pharo-ci-jenkins2＠inria.fr Jan. 22, 2019

Jan. 22, 2019

There is a new Pharo build available! The status of the build #140 was: SUCCESS. Could not extract further issue information from commit message: fix upload of release versions Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #139: FAILURE
by ci-pharo-ci-jenkins2＠inria.fr Jan. 22, 2019

Jan. 22, 2019

There is a new Pharo build available! The status of the build #139 was: FAILURE. Could not extract further issue information from commit message: fix upload of release versions Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #138: FAILURE
by ci-pharo-ci-jenkins2＠inria.fr Jan. 22, 2019

Jan. 22, 2019

There is a new Pharo build available! The status of the build #138 was: FAILURE. Could not extract further issue information from commit message: fix upload of release versions Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #17: SUCCESS
by ci-pharo-ci-jenkins2＠inria.fr Jan. 22, 2019

Jan. 22, 2019

There is a new Pharo build available! The status of the build #17 was: SUCCESS. Could not extract further issue information from commit message: Merge branch 'Pharo7.0' into Pharo8.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #136: SUCCESS
by ci-pharo-ci-jenkins2＠inria.fr Jan. 22, 2019

Jan. 22, 2019

There is a new Pharo build available! The status of the build #136 was: SUCCESS. Could not extract further issue information from commit message: fix upload of release versions Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0