April 2018 - Pharo-dev - lists.pharo.org

Environment variables encoding ?

by Sven Van Caekenberghe

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 is however a bit unclear how these are encoded. On macOS & *nix that seems to be UTF8, on Windows there are some reports that it appears to be Latin1 - but both might be locale specific, I don't know either way. Does anyone know for sure ? I furthermore think that OSEnvironment and its subclasses, who do this call, should be responsible for decoding the C strings into proper Pharo strings, and not leave that responsibility to its users. Fundamentally, in the following, the decoding is still not done correctly and that is wrong/confusing IMHO. $ FOO=benoÃ®t ./pharo Pharo.image eval 'OSEnvironment current associations' {'TERM_PROGRAM'->'Apple_Terminal'. 'TERM'->'xterm-256color'. 'SHELL'->'/bin/bash'. 'TMPDIR'->'/var/folders/sy/sndrtj9j1tq06j0lfnshmrl80000gn/T/'. 'FOO'->'benoÃÂ®t'. 'Apple_PubSub_Socket_Render'->'/private/tmp/com.apple.launchd.uWk7pivcLT/Render'. 'TERM_PROGRAM_VERSION'->'404'. 'TERM_SESSION_ID'->'845BECCD-0AB0-4686-B7F9-3A0FF84BDCB7'. 'USER'->'sven'. 'SSH_AUTH_SOCK'->'/private/tmp/com.apple.launchd.y5oCwdUyaG/Listeners'. 'PATH'->'/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/texbin:/opt/X11/bin'. 'PWD'->'/tmp/benoiÃÂt'. 'XPC_FLAGS'->'0x0'. 'XPC_SERVICE_NAME'->'0'. 'HOME'->'/Users/sven'. 'SHLVL'->'2'. 'LOGNAME'->'sven'. 'LC_CTYPE'->'UTF-8'. 'DISPLAY'->'/private/tmp/com.apple.launchd.lsgASYFiWW/org.macosforge.xquartz:0'. 'SECURITYSESSIONID'->'186a9'. 'OLDPWD'->'/tmp/benoiÃÂt'. '_'->'/tmp/benoiÃÂt/pharo-vm/Pharo.app/Contents/MacOS/Pharo'. '__CF_USER_TEXT_ENCODING'->'0x1F5:0x0:0x0'} Of course, if we change this, we will need to fix callers. Opinions ? Sven PS: Furthermore, I note that there is a subtle difference in how $FOO and $PWD in the above are UTF-8 encoded. In the former, normalisation was done, in the latter not. Maybe that could lead to problems (when comparing/composing them). This is a difficult/complex subject (https://medium.com/concerning-pharo/an-implementation-of-unicode-normalizat…)

April 17, 2018

[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

by ci-pharo-ci-jenkins2＠inria.fr

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: https://github.com/pharo-project/pharo/pull/1205 Issue Url: https://pharo.fogbugz.com/f/cases/21715 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 17, 2018

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

by ci-pharo-ci-jenkins2＠inria.fr

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: https://pharo.fogbugz.com/f/cases/21716 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 17, 2018

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

by Sven Van Caekenberghe

> On 17 Apr 2018, at 06:02, monty <monty2(a)programmer.net> wrote: > > https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/1820/console Yes, I know, the whole CI infrastructure is down I guess ...

April 17, 2018

pharo-contribution CI machines out of disk space

by monty

https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/1820/console

April 17, 2018

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

by Eliot Miranda

Hi Phil, On Mon, Apr 16, 2018 at 12:54 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > I have downloaded the https://github.com/pharo- > project/pharo-vm/blob/master/opensmalltalk-vm/build. > win32x86/pharo.cog.spur.lowcode/Pharo.exe.manifest and put it in the > folder that contains the PharoLauncher Pharo.exe and then the pointers are > correct again (they have their masking done correctly. > Good! > So, there is a packaging issue somewhere for Pharo Windows VMs as > downloaded by the Laucher. > Indeed, we must include the manifest files on Windows. > > Phil > > On Mon, Apr 16, 2018 at 12:45 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > Eliot, > > Thx for the pointer. > > No, there is no such file in the vm folder that is launching the Pharo > Launcher nor is there one in the vms folders that are downloaded to run the > various images started by the launcher. > > This manifest file is new to me. Where is it to be found and what does it > do for Pharo? > It must lie alongside the .exe. It's an XML file that specifies various runtime environment settings for the executable. i don't know all that it can do, I just know that it does seem whether an application is highDpi aware or not, and your bug report seems to point directly to this. Here's the manifest for Pharo: Pharo.exe.manifest <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3"> <assemblyIdentity version="1.0.0.0" processorArchitecture="*" name="www.mirandabanda.org.Cog.Pharo" type="win32" /> <description>Pharo Smalltalk Virtual Machine</description> <asmv3:application> <asmv3:windowsSettings xmlns=" http://schemas.microsoft.com/SMI/2005/WindowsSettings"> <dpiAware>false</dpiAware> </asmv3:windowsSettings> </asmv3:application> <dependency> <dependentAssembly> <assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="*" publicKeyToken="6595b64144ccf1df" language="*" /> </dependentAssembly> </dependency> </assembly> And that reminds me that they need to get updated to refer to opensmalltalk.org!! > Phil > > On Mon, Apr 16, 2018 at 5:29 PM, Eliot Miranda <eliot.miranda(a)gmail.com> > wrote: > >> Hi Phil, >> >> On Apr 16, 2018, at 8:16 AM, philippe.back(a)highoctane.be < >> philippe.back(a)gmail.com> wrote: >> >> I guess that it is what I installed and it works fine on my Win 10 system. >> >> Nice icon BTW. >> >> Now there is an issue with the mouse pointer in the launcher and all >> pther images (so maybe a VM problem). >> >> The cursor is all black and tiny and has no white surroundings. In a dark >> theme the cursor is close to invisible. >> >> Also the cursor is not obeying the magnification setting of Windows. It >> worked before. >> >> >> I guess that the cursor masks are not applied properly + other new stuff. >> >> >> Is the manifest (Pharo.exe.manifest ?) being installed? >> >> >> That is ruining the whole Pharo experience for me (and I guess newcomers). >> >> >> Phil >> >> On Mon, Apr 16, 2018, 16:14 Christophe Demarey < >> christophe.demarey(a)inria.fr> wrote: >> >>> Hi, >>> >>> Regarding the various problems Pharo Launchers had on Windows, we worked >>> on a new installer based on Advanced Installer [1] to avoid UAC (User >>> Account Control) and write permissions problems. This new installer now >>> installs Pharo Launcher in the userâs local app data folder (where for >>> sure, he has write permissions). Pharo Launcher also now have its own icon >>> and use its own name instead of Pharo. Also, the uninstaller now works as >>> expected. Last but not least, the installer is now signed to avoid warning >>> of Windows Defender. >>> Thanks to Ben Coman who did the first version of the packaging using >>> Advanced Installer (was NSIS). >>> This version should also improve the launch of Pharo images on Windows. >>> >>> So, please could you install and test this new version: and report any >>> problem with it? http://files.pharo.org/pharo-launcher/win-alpha/ >>> We do not have windows users around so itâs hard to know if it works >>> outside our tests boxes. >>> >>> Thanks, >>> Christophe >>> >>> [1] https://www.advancedinstaller.com/ >>> >> > -- _,,,^..^,,,_ best, Eliot

April 16, 2018

Re: [Pharo-dev] Esteban's ChangeLog week of 9 April 2018

by Esteban Lorenzano

yes, but I didnât write it in my log so is not reported ;) > On 16 Apr 2018, at 17:55, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > EstebanLM wrote >> 13 April 2018â¦ I just promoted new VMs as stable. > > Weren't those reverted? > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

April 16, 2018

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

by phil＠highoctane.be

I have downloaded the https://github.com/pharo-project/pharo-vm/blob/master/opensmalltalk-vm/buil… and put it in the folder that contains the PharoLauncher Pharo.exe and then the pointers are correct again (they have their masking done correctly. So, there is a packaging issue somewhere for Pharo Windows VMs as downloaded by the Laucher. Phil On Mon, Apr 16, 2018 at 5:29 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi Phil, > > On Apr 16, 2018, at 8:16 AM, philippe.back(a)highoctane.be < > philippe.back(a)gmail.com> wrote: > > I guess that it is what I installed and it works fine on my Win 10 system. > > Nice icon BTW. > > Now there is an issue with the mouse pointer in the launcher and all pther > images (so maybe a VM problem). > > The cursor is all black and tiny and has no white surroundings. In a dark > theme the cursor is close to invisible. > > Also the cursor is not obeying the magnification setting of Windows. It > worked before. > > > I guess that the cursor masks are not applied properly + other new stuff. > > > Is the manifest (Pharo.exe.manifest ?) being installed? > > > That is ruining the whole Pharo experience for me (and I guess newcomers). > > > Phil > > On Mon, Apr 16, 2018, 16:14 Christophe Demarey < > christophe.demarey(a)inria.fr> wrote: > >> Hi, >> >> Regarding the various problems Pharo Launchers had on Windows, we worked >> on a new installer based on Advanced Installer [1] to avoid UAC (User >> Account Control) and write permissions problems. This new installer now >> installs Pharo Launcher in the userâs local app data folder (where for >> sure, he has write permissions). Pharo Launcher also now have its own icon >> and use its own name instead of Pharo. Also, the uninstaller now works as >> expected. Last but not least, the installer is now signed to avoid warning >> of Windows Defender. >> Thanks to Ben Coman who did the first version of the packaging using >> Advanced Installer (was NSIS). >> This version should also improve the launch of Pharo images on Windows. >> >> So, please could you install and test this new version: and report any >> problem with it? http://files.pharo.org/pharo-launcher/win-alpha/ >> We do not have windows users around so itâs hard to know if it works >> outside our tests boxes. >> >> Thanks, >> Christophe >> >> [1] https://www.advancedinstaller.com/ >> >

April 16, 2018

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

by phil＠highoctane.be

Eliot, Thx for the pointer. No, there is no such file in the vm folder that is launching the Pharo Launcher nor is there one in the vms folders that are downloaded to run the various images started by the launcher. This manifest file is new to me. Where is it to be found and what does it do for Pharo? Phil On Mon, Apr 16, 2018 at 5:29 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi Phil, > > On Apr 16, 2018, at 8:16 AM, philippe.back(a)highoctane.be < > philippe.back(a)gmail.com> wrote: > > I guess that it is what I installed and it works fine on my Win 10 system. > > Nice icon BTW. > > Now there is an issue with the mouse pointer in the launcher and all pther > images (so maybe a VM problem). > > The cursor is all black and tiny and has no white surroundings. In a dark > theme the cursor is close to invisible. > > Also the cursor is not obeying the magnification setting of Windows. It > worked before. > > > I guess that the cursor masks are not applied properly + other new stuff. > > > Is the manifest (Pharo.exe.manifest ?) being installed? > > > That is ruining the whole Pharo experience for me (and I guess newcomers). > > > Phil > > On Mon, Apr 16, 2018, 16:14 Christophe Demarey < > christophe.demarey(a)inria.fr> wrote: > >> Hi, >> >> Regarding the various problems Pharo Launchers had on Windows, we worked >> on a new installer based on Advanced Installer [1] to avoid UAC (User >> Account Control) and write permissions problems. This new installer now >> installs Pharo Launcher in the userâs local app data folder (where for >> sure, he has write permissions). Pharo Launcher also now have its own icon >> and use its own name instead of Pharo. Also, the uninstaller now works as >> expected. Last but not least, the installer is now signed to avoid warning >> of Windows Defender. >> Thanks to Ben Coman who did the first version of the packaging using >> Advanced Installer (was NSIS). >> This version should also improve the launch of Pharo images on Windows. >> >> So, please could you install and test this new version: and report any >> problem with it? http://files.pharo.org/pharo-launcher/win-alpha/ >> We do not have windows users around so itâs hard to know if it works >> outside our tests boxes. >> >> Thanks, >> Christophe >> >> [1] https://www.advancedinstaller.com/ >> >

April 16, 2018

Re: [Pharo-dev] File path encoding

by Sven Van Caekenberghe

Actually, (from another thread) I think that it is related to how environment variables are accessed. Consider: $ FOO=benoÃ®t ./pharo Pharo.image eval 'OSEnvironment current associations' {'TERM_PROGRAM'->'Apple_Terminal'. 'TERM'->'xterm-256color'. 'SHELL'->'/bin/bash'. 'TMPDIR'->'/var/folders/sy/sndrtj9j1tq06j0lfnshmrl80000gn/T/'. 'FOO'->'benoÃÂ®t'. 'Apple_PubSub_Socket_Render'->'/private/tmp/com.apple.launchd.uWk7pivcLT/Render'. 'TERM_PROGRAM_VERSION'->'404'. 'TERM_SESSION_ID'->'845BECCD-0AB0-4686-B7F9-3A0FF84BDCB7'. 'USER'->'sven'. 'SSH_AUTH_SOCK'->'/private/tmp/com.apple.launchd.y5oCwdUyaG/Listeners'. 'PATH'->'/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/texbin:/opt/X11/bin'. 'PWD'->'/tmp/benoiÃÂt'. 'XPC_FLAGS'->'0x0'. 'XPC_SERVICE_NAME'->'0'. 'HOME'->'/Users/sven'. 'SHLVL'->'2'. 'LOGNAME'->'sven'. 'LC_CTYPE'->'UTF-8'. 'DISPLAY'->'/private/tmp/com.apple.launchd.lsgASYFiWW/org.macosforge.xquartz:0'. 'SECURITYSESSIONID'->'186a9'. 'OLDPWD'->'/tmp/benoiÃÂt'. '_'->'/tmp/benoiÃÂt/pharo-vm/Pharo.app/Contents/MacOS/Pharo'. '__CF_USER_TEXT_ENCODING'->'0x1F5:0x0:0x0'} As you can see, several values are wrongly decoded - and this is on macOS as well. > On 16 Apr 2018, at 15:10, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > >> On 16 Apr 2018, at 14:51, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> >> Hi Sven, >> >> On 16 April 2018 at 13:57, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> Technically, at the File (FilePlugin) level we seem to be able to handle paths with strange characters, even on Windows, but somehow, somewhere a bogus call is made during image startup. >> >> I'm not going to have time to look at this in the next few days, sorry. >> >> But I have a vague memory that some of the other primitives outside >> FilePlugin don't add the "\\?\" prefix, so they possibly also don't do >> wide character conversion. > > Then I hope some other Windows user/developer can have a look. > Hell, I believe we got a few French people working on Pharo, n'est pas ? > >> Cheers, >> Alistair

April 16, 2018