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

XMLHTTP[Request|Response]>>#testAddHeader #testHeaderValuesAdd - Zinc HTTPComponents

by Sven Van Caekenberghe

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

Feb. 14, 2019

[Pharo 8.0] Build #75: 2373-Tonel test is failing

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

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…

Feb. 14, 2019

Re: [Pharo-dev] Can't Install Launcher on Mac Mojave

by Christophe Demarey

https://github.com/pharo-project/pharo-launcher/issues/311 > Le 14 fÃ©vr. 2019 Ã 10:57, Christophe Demarey <christophe.demarey(a)inria.fr> a Ã©crit : > >> >> Le 13 fÃ©vr. 2019 Ã 19:23, Sean P. DeNigris <sean(a)clipperadams.com> a Ã©crit : >> >> Max Leske wrote >>> Nope. I downloaded launcher just 20 minutes ago on Mojave and am using >>> it without problems. >> >> Weird. Nuked startup preferences folder just in case. fullPath modification >> didn't help. >> >>> Where did you extract it to? >> ~/Application >> >>> Did you extract it as a different user? >> Doesn't look like it >> >>> Did you try to run it from within the .dmg directly? >> No. Opened the dmg, dragged it into apps folder, then opened that > > ok. I see. > When building PharoLauncher, Metacello loads PL code with url: > Metacello new > baseline: 'PharoLauncherâ; > repository: 'gitlocal://src'; > load > In PL, if you inspect IceRepository registry, you will notice a repository IceLibGitRepository(.) corresponding to the above expression. > when you run PL from UI, working directory is /, IceLibGitRepository(.) then is resolved to / => no git repo there. > Thatâs why you get: Could not find repository from â/' > > Here is a fix for it: > (IceRepository registeredRepositoryIncludingPackage: (RPackageOrganizer default packageNamed: 'PharoLauncher-Core')) > name: 'pharo-launcher'; > location: nil > > Christophe

Feb. 14, 2019

Re: [Pharo-dev] Can't Install Launcher on Mac Mojave

by Christophe Demarey

> Le 13 fÃ©vr. 2019 Ã 19:23, Sean P. DeNigris <sean(a)clipperadams.com> a Ã©crit : > > Max Leske wrote >> Nope. I downloaded launcher just 20 minutes ago on Mojave and am using >> it without problems. > > Weird. Nuked startup preferences folder just in case. fullPath modification > didn't help. > >> Where did you extract it to? > ~/Application > >> Did you extract it as a different user? > Doesn't look like it > >> Did you try to run it from within the .dmg directly? > No. Opened the dmg, dragged it into apps folder, then opened that ok. I see. When building PharoLauncher, Metacello loads PL code with url: Metacello new baseline: 'PharoLauncherâ; repository: 'gitlocal://src'; load In PL, if you inspect IceRepository registry, you will notice a repository IceLibGitRepository(.) corresponding to the above expression. when you run PL from UI, working directory is /, IceLibGitRepository(.) then is resolved to / => no git repo there. Thatâs why you get: Could not find repository from â/' Here is a fix for it: (IceRepository registeredRepositoryIncludingPackage: (RPackageOrganizer default packageNamed: 'PharoLauncher-Core')) name: 'pharo-launcher'; location: nil Christophe

Feb. 14, 2019

Re: [Pharo-dev] Can't Install Launcher on Mac Mojave

by Max Leske

I downloaded it again, extracted it to /Applications, ran Pharo7-64bit and opened Iceberg without issues. Launcher created the working directory at ~/Documents/Pharo, which should be fine w.r.t. permissions. I'm out of ideas... On 13 Feb 2019, at 19:23, Sean P. DeNigris wrote: > Max Leske wrote >> Nope. I downloaded launcher just 20 minutes ago on Mojave and am >> using >> it without problems. > > Weird. Nuked startup preferences folder just in case. fullPath > modification > didn't help. > >> Where did you extract it to? > ~/Application > >> Did you extract it as a different user? > Doesn't look like it > >> Did you try to run it from within the .dmg directly? > No. Opened the dmg, dragged it into apps folder, then opened that > > > > ----- > Cheers, > Sean > -- > Sent from: > http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 14, 2019

Re: [Pharo-dev] DeleteVisitor and symbolic links

by Alistair Grant

Hi Sven & Torsten, On Wed, 13 Feb 2019 at 20:59, Torsten Bergmann <astares(a)gmx.de> wrote: > > Sven wrote: > > Thanks, Alistair, for taking care of all this stuff. > > +1 Thank you! Cheers, Alistair

Feb. 14, 2019

Re: [Pharo-dev] DeleteVisitor and symbolic links

by Nicolas Cellier

+1, following links is insanely dangerous Le mer. 13 fÃ©vr. 2019 Ã 20:59, Torsten Bergmann <astares(a)gmx.de> a Ã©crit : > Sven wrote: > > Thanks, Alistair, for taking care of all this stuff. > > +1 > >

Feb. 13, 2019

Re: [Pharo-dev] External Module not found

by Esteban Lorenzano

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> >

Feb. 13, 2019

Re: [Pharo-dev] DeleteVisitor and symbolic links

by Torsten Bergmann

Sven wrote: > Thanks, Alistair, for taking care of all this stuff. +1

Feb. 13, 2019

Re: [Pharo-dev] DeleteVisitor and symbolic links

by Sven Van Caekenberghe

Thanks, Alistair, for taking care of all this stuff. > On 13 Feb 2019, at 18:54, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > 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 >

Feb. 13, 2019