- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #77: 2531-Removing-global-action-Introduce-DisplayableObject-
by ci-pharo-ci-jenkins2＠inria.fr Feb. 14, 2019

Feb. 14, 2019

There is a new Pharo build available! The status of the build #77 was: FAILURE. The Pull Request #2533 was integrated: "2531-Removing-global-action-Introduce-DisplayableObject-" Pull request url: https://github.com/pharo-project/pharo/pull/2533 Issue Url: https://pharo.fogbugz.com/f/cases/2531 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #76: 2529-MenuRegistration-MenuSpec-tag-should-be-merged-into-Core
by ci-pharo-ci-jenkins2＠inria.fr Feb. 14, 2019

Feb. 14, 2019

There is a new Pharo build available! The status of the build #76 was: SUCCESS. The Pull Request #2532 was integrated: "2529-MenuRegistration-MenuSpec-tag-should-be-merged-into-Core" Pull request url: https://github.com/pharo-project/pharo/pull/2532 Issue Url: https://pharo.fogbugz.com/f/cases/2529 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

XMLHTTP[Request|Response]>>#testAddHeader #testHeaderValuesAdd - Zinc HTTPComponents
by Sven Van Caekenberghe Feb. 14, 2019

Feb. 14, 2019

Hi, I noticed that some tests from XML Support started failing with the latest version of Zinc. The 4 tests are XMLHTTP[Request|Response]>>#testAddHeader #testHeaderValuesAdd And yes, something changed recently (a couple of months ago) in Zinc: ZnMultiValueDictionary>>#at:add: became idempotent (by design). ZnMultiValueDictionary is like a dictionary but allows for multiple entries per key. In practice this is used for the headers of an HTTP request or response and for the query values of a URL. Using the second application as an example, this means that http://server.com/foo?a=1&b=2 contains 2 simple key/value pairs (a=1 and b=2), while http://server.com/foo?a=1&b=2&a=-1 contains 1 normal key (b=2) and 1 extended key with 2 values (a=1 and a=-1). With the recent change, http://server.com/foo?a=1&b=2&a=-1&b=2 is the same (idempotent) as the previous one, since b=2 occurs twice with exactly the same key and value. XMLHTTP[Request|Response]>>#testAddHeader #testHeaderValuesAdd assume that adding the same key and value more than once should be relevant (not be idempotent). In HTTP headers, this means that Connection:close can occur multiple times but that that would be totally equivalent to it occurring only once. I think that XMLHTTP is wrong and Zinc is right. Opinions ? Sven

1 0

[Pharo 8.0] Build #75: 2373-Tonel test is failing
by ci-pharo-ci-jenkins2＠inria.fr Feb. 14, 2019

Feb. 14, 2019

There is a new Pharo build available! The status of the build #75 was: SUCCESS. The Pull Request #2530 was integrated: "2373-Tonel test is failing" Pull request url: https://github.com/pharo-project/pharo/pull/2530 Issue Url: https://pharo.fogbugz.com/f/cases/Pharo8.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

DeleteVisitor and symbolic links
by Alistair Grant Feb. 14, 2019

Feb. 14, 2019

Hi Everyone, I inadvertantly changed the behaviour of DeleteVisitor in Pharo 8. In Pharo 7 DeleteVisitor will follow all symbolic links when deleting a directory tree. This has two consequences: - A symbolic link that points to its containing directory will result in an infinite loop. - Files may be deleted that are NOT subdirectories of the root directory. The Pharo 8 behaviour of not following symbolic links is how the linux 'rm -r' command behaves, and how I think DeleteVisitor should behave. As Sean commented in http://forum.world.st/File-problems-in-Pharo-8-tp5095111p5095176.html following symbolic links can lead to unexpected behaviour, deleting files out of the tree, and thus is quite dangerous. But since it is a change in existing behaviour, I wanted to let everyone know in case there's something I haven't thought of. I'll submit a PR that updates the appropriate method and class comments in a few days. Cheers, Alistair

4 4

Re: [Pharo-dev] External Module not found
by Esteban Lorenzano Feb. 13, 2019

Feb. 13, 2019

Hi, > On 13 Feb 2019, at 15:06, Moussa Saker via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Moussa Saker <sak_moussa(a)yahoo.fr> > Subject: Re: [Pharo-dev] External Module not found > Date: 13 February 2019 at 15:06:12 CET > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Reply-To: Moussa Saker <sak_moussa(a)yahoo.fr> > > > the missing module is SqueakFFIPrims as shown by the debuger > <Screenshot from 2019-02-13 14.33.17.png> > how i can add it ? No is not. Youâre missing Cairo library. Most probably you can install it with apt-get etc. Esteban > > Moussa. > > > On Wednesday, 13 February 2019, 09:10:22 CET, Pierce Ng <pierce(a)samadhiweb.com> wrote: > > > On Wed, Feb 13, 2019 at 12:12:39AM +0000, Moussa Saker via Pharo-dev wrote: > > > am using a Pharo 7 image and an elementary os 64bits distribution > > (based on Ubuntu 18.04), i was working on my project and when trying > > to execute it i encountered this problem. > > > Click on the debug button, look around and it'll tell you _which_ > external module cannot be found. From context it looks like Cairo, so > try installing Cairo runtime libraries, but before that confirm by > clicking on the debug button. > > > > > <Screenshot from 2019-02-13 14.33.17.png> >

1 0

[Pharo 8.0] Build #74: 2518-DiskStoreentryFromNodepathfor-doesnt-use-existing-attributes
by ci-pharo-ci-jenkins2＠inria.fr Feb. 13, 2019

Feb. 13, 2019

There is a new Pharo build available! The status of the build #74 was: FAILURE. The Pull Request #2522 was integrated: "2518-DiskStoreentryFromNodepathfor-doesnt-use-existing-attributes" Pull request url: https://github.com/pharo-project/pharo/pull/2522 Issue Url: https://pharo.fogbugz.com/f/cases/2518 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #73: 2219-RBParseErrorNode-misses-dumpOn
by ci-pharo-ci-jenkins2＠inria.fr Feb. 13, 2019

Feb. 13, 2019

There is a new Pharo build available! The status of the build #73 was: SUCCESS. The Pull Request #2524 was integrated: "2219-RBParseErrorNode-misses-dumpOn" Pull request url: https://github.com/pharo-project/pharo/pull/2524 Issue Url: https://pharo.fogbugz.com/f/cases/2219 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #72: 2205-OCASTTranslator-class-initialize-should-not-invoke-super
by ci-pharo-ci-jenkins2＠inria.fr Feb. 13, 2019

Feb. 13, 2019

There is a new Pharo build available! The status of the build #72 was: SUCCESS. The Pull Request #2520 was integrated: "2205-OCASTTranslator-class-initialize-should-not-invoke-super" Pull request url: https://github.com/pharo-project/pharo/pull/2520 Issue Url: https://pharo.fogbugz.com/f/cases/2205 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #71: 2189-superNodeClass-selfNodeClass-and-thisContextNodeClass-are-not-used-
by ci-pharo-ci-jenkins2＠inria.fr Feb. 13, 2019

Feb. 13, 2019

There is a new Pharo build available! The status of the build #71 was: SUCCESS. The Pull Request #2521 was integrated: "2189-superNodeClass-selfNodeClass-and-thisContextNodeClass-are-not-used-" Pull request url: https://github.com/pharo-project/pharo/pull/2521 Issue Url: https://pharo.fogbugz.com/f/cases/2189 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0