- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #951: 21966-bindings-ok-to-use-array-of-associations
by ci-pharo-ci-jenkins2＠inria.fr May 25, 2018

May 25, 2018

There is a new Pharo build available! The status of the build #951 was: SUCCESS. The Pull Request #1413 was integrated: "21966-bindings-ok-to-use-array-of-associations" Pull request url: https://github.com/pharo-project/pharo/pull/1413 Issue Url: https://pharo.fogbugz.com/f/cases/21966 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #950: 21925-SharedPool-subclasses-should-not-trigger-class-not-referenced--QA-Rule-if-they-are-used
by ci-pharo-ci-jenkins2＠inria.fr May 25, 2018

May 25, 2018

There is a new Pharo build available! The status of the build #950 was: FAILURE. The Pull Request #1381 was integrated: "21925-SharedPool-subclasses-should-not-trigger-class-not-referenced--QA-Rule-if-they-are-used" Pull request url: https://github.com/pharo-project/pharo/pull/1381 Issue Url: https://pharo.fogbugz.com/f/cases/21925 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #949: 21965-SmaltlalkImagecompiler--use-globals-as-default-environment-not-just-self
by ci-pharo-ci-jenkins2＠inria.fr May 25, 2018

May 25, 2018

There is a new Pharo build available! The status of the build #949 was: FAILURE. The Pull Request #1416 was integrated: "21965-SmaltlalkImagecompiler--use-globals-as-default-environment-not-just-self" Pull request url: https://github.com/pharo-project/pharo/pull/1416 Issue Url: https://pharo.fogbugz.com/f/cases/21965 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #948: 21956-tiny-cleanup-simplify-methods-related-to-pools-in-Class
by ci-pharo-ci-jenkins2＠inria.fr May 25, 2018

May 25, 2018

There is a new Pharo build available! The status of the build #948 was: FAILURE. The Pull Request #1409 was integrated: "21956-tiny-cleanup-simplify-methods-related-to-pools-in-Class" Pull request url: https://github.com/pharo-project/pharo/pull/1409 Issue Url: https://pharo.fogbugz.com/f/cases/21956 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] [Pharo-users] pharo location include korean charactor then look is not good.
by Sven Van Caekenberghe May 25, 2018

May 25, 2018

I made the following quick changes: UnixEnvironment>>#environAt: index ^ (self environ at: index) ifNotNil: [ :string | string asByteArray utf8Decoded ] OSPlatform>>#currentWorkingDirectoryPathWithBuffer: aByteString <primitive: 'primitiveGetCurrentWorkingDirectory' module: '' error: ec> ^ (self getPwdViaFFI: aByteString size: aByteString size) ifNotNil: [ :string | string asByteArray utf8Decoded ] ifNil:[ self error:'Insufficient buffer size to read current working directory: ' , aByteString size asString] But actually almost any string coming from the VM seems wrong (i.e. should be further UTF-8 decoded): SmalltalkImage>>#[prim]ImagePath and #vmFileName basically probably every call VirtualMachine>>#getSystemAttribute: what a mess ... > On 25 May 2018, at 10:49, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > We looked at this before, but came to no conclusion. > > The problem lies with OS environment variable decoding. > > I created a 64-bit Pharo 7 in /tmp/Ã©tÃ© on macOS. > > FileLocator imageDirectory resolve. > "File @ /private/tmp/Ã©tÃ©" > > Smalltalk os environment at: 'PWD'. > "'/tmp/ÃÂ©tÃÂ©'" > > (Smalltalk os environment at: 'PWD') asByteArray utf8Decoded. > "'/tmp/Ã©tÃ©'" > > Smalltalk os environment asDictionary. > > FileBrowser works OK too but starts up with a wrong window title. > > I believe the real issue is that we are not 100% sure that it is always UTF8 on all platforms all the time (i.e. apparently users can put their (Windows) OS in a different encoding). > >> On 25 May 2018, at 10:28, Hilaire <hilaire(a)drgeo.eu> wrote: >> >> I second you on this issue. Something went wrong in the encoding in the path in your window title. Ã smells like UTF-8 issue. >> >> Looks like Pharo7 still has some issue(s) when handling UTF-8 characters used in modern Operating System filling system. >> >> Another example of this problem, with DrGeo copied in a path with UTF-8 characters, for example ÃtÃ© folder. When DrGeo is started, Pharo creates a folder ÃÂtÃÂ© where it creates some locale/ folder >> >> I see this problem on ubtuntu 17.10 and Mac OSX at my school. >> >> We have this problem for years, I was believing it was fixed, but apparently not. >> >> Hilaire >> >> >> Le 25/05/2018 Ã 04:09, peter yoo a Ã©crit : >>> so.. application location include korean charactor then broken title string in pharo window. >>> (of course ubuntu 18.04 with gnome env) >>> >>> broken title is "ë°ííë©´". it's ok? or where to report? >>> >>> look a attached file please. >>> >>> -- >> >> -- >> Dr. Geo >> http://drgeo.eu >> >> <P7-utf8.png> >

1 0

[Pharo 7.0-dev] Build #947: 21781-trait-composition-should-not-copy-slots-everytime-it-is-asked
by ci-pharo-ci-jenkins2＠inria.fr May 25, 2018

May 25, 2018

There is a new Pharo build available! The status of the build #947 was: SUCCESS. The Pull Request #1253 was integrated: "21781-trait-composition-should-not-copy-slots-everytime-it-is-asked" Pull request url: https://github.com/pharo-project/pharo/pull/1253 Issue Url: https://pharo.fogbugz.com/f/cases/21781 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #946: 21954-cleanup-copyOfMethodDictionary-and-copyMethodDictionaryFrom
by ci-pharo-ci-jenkins2＠inria.fr May 25, 2018

May 25, 2018

There is a new Pharo build available! The status of the build #946 was: FAILURE. The Pull Request #1408 was integrated: "21954-cleanup-copyOfMethodDictionary-and-copyMethodDictionaryFrom" Pull request url: https://github.com/pharo-project/pharo/pull/1408 Issue Url: https://pharo.fogbugz.com/f/cases/21954 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

files.pharo.org, get.pharo.org problems?
by Martin McClure May 24, 2018

May 24, 2018

I'm getting 503 errors on attempts to contact both sites -- is this a known issue? Regards, -Martin

6 7

Pharo 7 Launch Failure - Freetype Problem?
by Sean P. DeNigris May 24, 2018

May 24, 2018

Following the contribution instructions on the website [1] to review the PR for issue 15230 [2], I downloaded the build artifact [3] from the validation [4]. When I tried to launch it a few times (Mac 10.13.2), it showed in the app list, but never opened a window. I did a force quit and found a debug log [5], which shows a few errors from different startup attempts which all seem to trace back to Freetype. The latest was "Could not find accessor for variable named "'dest'"" from "FFICallout>>loaderForArgNamed:", and further down I found "FreeTypeExternalMemory>>primCopyToExternalMemory:" 1. https://pharo.org/review-fix 2. https://github.com/pharo-project/pharo/pull/1383 3. https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… 4. https://ci.inria.fr/pharo-ci-jenkins2/blue/organizations/jenkins/Test%20pen… 5. https://gist.github.com/seandenigris/d153ff4757f681c5169a29cf832ca31a ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

3 4

[Iceberg] Call for contributions
by Guillermo Polito May 24, 2018

May 24, 2018

Hi everybody, just for information, we have gathered some ideas on possible contributions for iceberg besides those in the issue tracker. We've put that in Iceberg's wiki: https://github.com/pharo-vcs/iceberg/wiki/How-to-help-us,-What-you-could-co… The idea is that those contributions are mini-projects on themselves, that could even have an usage outside Iceberg. Cheers, Guille

1 0