[Pharo-dev] [Pharo 7.0-dev] Build #772: 21715-When-asking-for-the-context-in-a-after-node-on-a-method-return-context-of-method-not-the-ensure-block

There is a new Pharo build available! The status of the build #772 was: SUCCESS. The Pull Request #1205 was integrated: "21715-When-asking-for-the-context-in-a-after-node-on-a-method-return-context-of-method-not-the-ensure-block" Pull request url:

Re: [Pharo-dev] Environment variables encoding ?

It seems macOS normalizes UTF-8 differently from everyone else in file names (I think base character + composing instead of precomposed codepoint). That might affect PWD. For environment variables, even if most sensible platforms should have adopted UTF-8 by now, I wouldn't be surprised if there's

Re: [Pharo-dev] Environment variables encoding ?

primitiveGetenv returns values in the current locale's code page on Windows; a value bound to € returns a stings with single char 128 on MS1252 (western european) at least. On windows, there are three versions of each api call with string parameters/returns; xxx (depending on UNICODE being

[Pharo-dev] Environment variables encoding ?

Hi, The dictionary OSPlatform current environment contains a copy of the OS's environment variables (more correctly of the VM process), as key/value pairs. These are obtained via the following system calls: on macOS & *nix LIBC environ on Windows KERNEL32 GetEnvironmentStrings It

Re: [Pharo-dev] Environment variables encoding ?

Yes, I also saw the *W variants, my initial reaction was that those would make more sense, but it is hard to see all consequences. > On 17 Apr 2018, at 10:49, Henrik Sperre Johansen > wrote: > > primitiveGetenv returns values in the current locale's code page on

Re: [Pharo-dev] [Pharo-Launcher] call for tests on Windows

Hi Phil, Eliot, > Le 16 avr. 2018 à 23:58, Eliot Miranda a écrit : > > Hi Phil, > > On Mon, Apr 16, 2018 at 12:54 PM, p...@highoctane.be > > > wrote: > I have downloaded the >

Re: [Pharo-dev] [Pharo-Launcher] call for tests on Windows

Hi Christophe, What Windows version do you have? I have Windows 10 and a 4K screen. Phil On Tue, Apr 17, 2018 at 9:43 AM, Christophe Demarey < christophe.dema...@inria.fr> wrote: > Hi Phil, Eliot, > > Le 16 avr. 2018 à 23:58, Eliot Miranda a écrit : > > Hi Phil, > >

Re: [Pharo-dev] Environment variables encoding ?

2018-04-17 10:05 GMT+02:00 Sven Van Caekenberghe : > > > > On 17 Apr 2018, at 09:57, Damien Pollet wrote: > > > > It seems macOS normalizes UTF-8 differently from everyone else in file > names (I think base character + composing instead of precomposed >

Re: [Pharo-dev] Environment variables encoding ?

Damien Pollet wrote > It seems macOS normalizes UTF-8 differently from everyone else in file > names (I think base character + composing instead of precomposed > codepoint). That might affect PWD. > For environment variables, even if most sensible platforms should have > adopted UTF-8 by now, I

Re: [Pharo-dev] Environment variables encoding ?

--- Begin Message --- I do remember clearly that while debugging that problem, the %LOCALAPPDATA% environment at some point kept that string encoded with Latin-1 (I'm on Windows 10, french version).  I have not been able to reproduce the exact sequence which led to that specific case

Re: [Pharo-dev] Environment variables encoding ?

> On 17 Apr 2018, at 09:57, Damien Pollet wrote: > > It seems macOS normalizes UTF-8 differently from everyone else in file names > (I think base character + composing instead of precomposed codepoint). That > might affect PWD. > For environment variables, even if

Re: [Pharo-dev] [Pharo-Launcher] call for tests on Windows

Windows 10 on top of virtual box > Le 17 avr. 2018 à 10:29, p...@highoctane.be a écrit : > > Hi Christophe, > > What Windows version do you have? > > I have Windows 10 and a 4K screen. > > Phil > > On Tue, Apr 17, 2018 at 9:43 AM, Christophe Demarey >

Re: [Pharo-dev] Environment variables encoding ?

> On 17 Apr 2018, at 10:40, Nicolai Hess wrote: > > > > 2018-04-17 10:05 GMT+02:00 Sven Van Caekenberghe : > > > > On 17 Apr 2018, at 09:57, Damien Pollet wrote: > > > > It seems macOS normalizes UTF-8 differently from

[Pharo-dev] [Pharo 7.0-dev] Build #773: 21523-package-ReflectionMirrors-Primitives-needs-to-be-moved-to-the-BaselineOfPharoBootstrap

There is a new Pharo build available! The status of the build #773 was: SUCCESS. The Pull Request #1051 was integrated: "21523-package-ReflectionMirrors-Primitives-needs-to-be-moved-to-the-BaselineOfPharoBootstrap" Pull request url: https://github.com/pharo-project/pharo/pull/1051

Re: [Pharo-dev] Pavel's ChangeLog week of 2018-02-05

On Tue, Apr 17, 2018 at 2:08 PM, Thierry Goubier wrote: > 2018-04-17 14:03 GMT+02:00 Clément Bera : > > Hi Pavel, > > > > I'm looking at PosixSharedMemory again since I have to write a Master > > student proposal and I think this could be a good

Re: [Pharo-dev] Pavel's ChangeLog week of 2018-02-05

2018-04-17 14:28 GMT+02:00 Clément Bera : > > > On Tue, Apr 17, 2018 at 2:08 PM, Thierry Goubier > wrote: >> >> 2018-04-17 14:03 GMT+02:00 Clément Bera : >> > Hi Pavel, >> > >> > I'm looking at PosixSharedMemory again

[Pharo-dev] [Pharo 7.0-dev] Build #774: 21429-Watchpoints-should-be-cleaned-when-system-changed

There is a new Pharo build available! The status of the build #774 was: FAILURE. The Pull Request #1162 was integrated: "21429-Watchpoints-should-be-cleaned-when-system-changed" Pull request url: https://github.com/pharo-project/pharo/pull/1162 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #775: Revert "21429-Watchpoints-should-be-cleaned-when-system-changed"

There is a new Pharo build available! The status of the build #775 was: SUCCESS. The Pull Request #1209 was integrated: "Revert "21429-Watchpoints-should-be-cleaned-when-system-changed"" Pull request url: https://github.com/pharo-project/pharo/pull/1209 Issue Url:

Re: [Pharo-dev] [Pharo 7.0-dev] Build #775: Revert "21429-Watchpoints-should-be-cleaned-when-system-changed"

It is nice how easy a faulty merge can be reverted now… > On 17 Apr 2018, at 13:33, ci-pharo-ci-jenki...@inria.fr wrote: > > There is a new Pharo build available! > > The status of the build #775 was: SUCCESS. > > The Pull Request #1209 was integrated: "Revert >

Re: [Pharo-dev] pharo-contribution CI machines out of disk space

> Le 17 avr. 2018 à 06:02, monty a écrit : > > https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/1820/console > You’re right. I did some cleaning and put slaves back on line. Thanks for the report.

Re: [Pharo-dev] Pavel's ChangeLog week of 2018-02-05

2018-04-17 14:03 GMT+02:00 Clément Bera : > Hi Pavel, > > I'm looking at PosixSharedMemory again since I have to write a Master > student proposal and I think this could be a good topic. I'm not really > expert on SharedMemory, so I'm going to share what I have in mind, we

Re: [Pharo-dev] Pavel's ChangeLog week of 2018-02-05

Hi Pavel, I'm looking at PosixSharedMemory again since I have to write a Master student proposal and I think this could be a good topic. I'm not really expert on SharedMemory, so I'm going to share what I have in mind, we can discuss about it, you could also co-supervise the student indirectly

[Pharo-dev] [Pharo 7.0-dev] Build #771: 21716 File size should be in accessing protocol

There is a new Pharo build available! The status of the build #771 was: SUCCESS. The Pull Request #1207 was integrated: "21716 File size should be in accessing protocol" Pull request url: https://github.com/pharo-project/pharo/pull/1207 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #776: 21722-Small-Cleanup-Syntax-highlighting-remove-a-reference-to-SHParserST80

There is a new Pharo build available! The status of the build #776 was: SUCCESS. The Pull Request #1210 was integrated: "21722-Small-Cleanup-Syntax-highlighting-remove-a-reference-to-SHParserST80" Pull request url: https://github.com/pharo-project/pharo/pull/1210 Issue Url:

Re: [Pharo-dev] pharo-contribution CI machines out of disk space

Yes we should. I started to keep the minimum on mine and remove some obsolete ones. The problem we have is that people forgot to remove their job when they do not need them anymore. Stef On Wed, Apr 18, 2018 at 5:05 AM, monty wrote: > Not quite fixed: >

[Pharo-dev] [Pharo 7.0-dev] Build #777: 21723-Opal-compiler-instances-are-created-in-huge-amount-during-a-method-compilation-from-the-browser

There is a new Pharo build available! The status of the build #777 was: FAILURE. The Pull Request #1212 was integrated: "21723-Opal-compiler-instances-are-created-in-huge-amount-during-a-method-compilation-from-the-browser" Pull request url:

Re: [Pharo-dev] pharo-contribution CI machines out of disk space

Not quite fixed: https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/1822/PHARO=30,VERSION=bleedingEdge,VM=vm/console Should we start reconfiguring jobs to keep fewer builds? > Sent: Tuesday, April 17, 2018 at 6:08 AM > From: "Christophe Demarey" > To: