June 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] strange difference between localhost and 127.0.0.1 with a Zinc server on mac

by Ben Coman

Sven Van Caekenberghe wrote: > In any case, the server socket used is normally listening on all interfaces [0.0.0.0] > > Sven > > Maybe it matters that [0.0.0.0] is the IPv4-Unspecified-Address and it might make a difference to use IPv6-Unspecified-Address [0:0:0:0:0:0:0:0] or [::] cheers -ben

June 14, 2014

Re: [Pharo-dev] strange difference between localhost and 127.0.0.1 with a Zinc server on mac

by Ben Coman

June 14, 2014

Re: [Pharo-dev] PharoVM with latests changes

by Pablo R. Digonzelli

Thanks!!! downloading.. Ing. Pablo Digonzelli Software Solutions IP-Solutiones SRL Metrotec SRL 25 de Mayo 521 Email: pdigonzelli(a)softsargentina.com pdigonzelli(a)gmail.com Cel: 5493815982714 ----- Mensaje original ----- De: "Esteban A. Maringolo" <emaringolo(a)gmail.com> Para: "Pharo Development List" <pharo-dev(a)lists.pharo.org> Enviados: MiÃ©rcoles, 11 de Junio 2014 17:32:02 Asunto: Re: [Pharo-dev] PharoVM with latests changes Thank you! I'm downloading it right now. Esteban A. Maringolo 2014-06-11 17:16 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi, > > Soâ¦ last days Iâve been working in new versions of the PharoVM based in > latest Eliot sources. > New vmâs can be found at: > > http://files.pharo.org/vm/pharo/ > http://files.pharo.org/vm/pharoS/ > > under âlatest.zipâ > > and you can also take it from zeroconf using âvmLatestâ > > and here is an explanation of what this work is so annoying: > > http://smallworks.eu/web/blog/2014-06-11-fighting-entropy > > So, please test, report, etc. > > Expectations: Everything is solved (including the annoying âsmall int bugâ) > and even faster than before. > Realistic expectations: Everything works fine, we are aligned to latest > sources, and now I can start working on the SpurVM implementation. > > Cheers, > Esteban

June 14, 2014

Re: [Pharo-dev] strange difference between localhost and 127.0.0.1 with a Zinc server on mac

by Sven Van Caekenberghe

I must admit that I haven't given the whole IPv6 issue much thought. It is good that you/users provide feedback, it is more an OS thing I think/hope. On 14 Jun 2014, at 11:37, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > Hi Sven, > > $ telnet localhost 1701 > works perfectly but I noticed that it first tries to connect to ::1 and then switch to 127.0.0.1 > > Trying ::1... > telnet: connect to address ::1: Connection refused > Trying 127.0.0.1... > Connected to localhost > > but I suspected that curl does the same and do not fallback to 127.0.0.1 > and yes this one works: > > curl --ipv4 http://localhost:1701 > > so by default my curl works on ipv6 > > I do not know why ::1 is before 127.0.0.1 on my mac 10.9.3. > Is there a global option? > in /etc/hosts 127.0.0.1 if first > > anyway, thanks > problem solved and not related with Zinc ;-) > > Luc > > > 2014-06-14 11:03 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > Luc, > > I have seen this kind of weirdness before, but I mostly see it with ab (apache benchmark tool). I really have no idea. Have you tried with telnet to do a manual HTTP request ? > > $ telnet localhost 1701 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > GET /random HTTP/1.1 > Host:localhost:1701 > > HTTP/1.1 200 OK > Content-Type: text/plain;charset=utf-8 > Content-Length: 64 > Date: Sat, 14 Jun 2014 08:58:48 GMT > Server: Zinc HTTP Components 1.0 > > EF97C091498F3FEA3F79F65D36C40ECAFD116A68BA31F45D027DB61EBDD1579 > ^] > telnet> close > Connection closed. > > You could also try using the same or a second Pharo image to do the request. > > $ ./pharo Pharo.image eval "ZnClient new get: 'http://localhost:8080/random'" > '766EF4E6E5664EF4C5163D30125B5C35BFE2AED408835CB6D6206DF0A7A15FD > ' > > In any case, the server socket used is normally listening on all interfaces [0.0.0.0] > > Sven > > On 14 Jun 2014, at 09:17, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > > > > > > > 2014-06-14 6:04 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > > Luc Fabresse wrote: > >> Hi, > >> > >> I experiencing a strange difference between localhost and 127.0.0.1. > >> > >> In Pharo I do: > >> > >> (ZnServer startDefaultOn: 4444) > >> onRequestRespond: [ :request | ZnResponse ok: (ZnEntity text: 'hello') ] > >> > >> In bash: > >> > >> $ lsof -Pi | grep Pharo > >> Pharo 2718 luc 7u IPv4 0x1e64a2e9381f409b 0t0 TCP *:4444 (LISTEN) > >> > >> I perfectly listen on port 4444 from all interfaces * > >> > >> $ curl http://127.0.0.1:4444 > >> hello > >> > >> $ curl http://localhost:4444 > >> curl: (7) Failed to connect to localhost port 4444: Connection refused <- why ? > >> > >> localhost is correctly resolved on my mac > >> $ ping localhost > >> PING localhost (127.0.0.1): 56 data bytes > >> 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.044 ms > >> > >> I tested with other programs than Zinc to open listening sockets and it works. > >> > >> Any idea? > >> > >> #Luc > > maybe http://sourceforge.net/p/curl/bugs/1337/ > > > > Humm, I use curl 7.36.0, so yes perhaps this bug fix is not integrated... > > > > Anyway, I was also suspecting curl but I tested with server: Apache on port 8888 and here curl works: > > > > httpd 621 luc 5u IPv6 0x6ea19c1d988f10db 0t0 TCP *:8888 <-- same as Zinc > > > > but both: > > > > curl http://127.0.0.1:8888 > > curl http://localhost:8888 > > > > are working. > > > > wget always works (Apache and Zinc): > > > > wget -qO- http://127.0.0.1:8888 > > wget -qO- http://localhost:8888 > > > > Thanks Max and Ben, > > > > Luc > > > > >

June 14, 2014

Re: [Pharo-dev] strange difference between localhost and 127.0.0.1 with a Zinc server on mac

by Luc Fabresse

Hi Sven, $ telnet localhost 1701 works perfectly but I noticed that it first tries to connect to ::1 and then switch to 127.0.0.1 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost but I suspected that curl does the same and do not fallback to 127.0.0.1 and yes this one works: curl --ipv4 http://localhost:1701 so by default my curl works on ipv6 I do not know why ::1 is before 127.0.0.1 on my mac 10.9.3. Is there a global option? in /etc/hosts 127.0.0.1 if first anyway, thanks problem solved and not related with Zinc ;-) Luc 2014-06-14 11:03 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > Luc, > > I have seen this kind of weirdness before, but I mostly see it with ab > (apache benchmark tool). I really have no idea. Have you tried with telnet > to do a manual HTTP request ? > > $ telnet localhost 1701 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > GET /random HTTP/1.1 > Host:localhost:1701 > > HTTP/1.1 200 OK > Content-Type: text/plain;charset=utf-8 > Content-Length: 64 > Date: Sat, 14 Jun 2014 08:58:48 GMT > Server: Zinc HTTP Components 1.0 > > EF97C091498F3FEA3F79F65D36C40ECAFD116A68BA31F45D027DB61EBDD1579 > ^] > telnet> close > Connection closed. > > You could also try using the same or a second Pharo image to do the > request. > > $ ./pharo Pharo.image eval "ZnClient new get: ' > http://localhost:8080/random'" > '766EF4E6E5664EF4C5163D30125B5C35BFE2AED408835CB6D6206DF0A7A15FD > ' > > In any case, the server socket used is normally listening on all > interfaces [0.0.0.0] > > Sven > > On 14 Jun 2014, at 09:17, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > > > > > > > 2014-06-14 6:04 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > > Luc Fabresse wrote: > >> Hi, > >> > >> I experiencing a strange difference between localhost and 127.0.0.1. > >> > >> In Pharo I do: > >> > >> (ZnServer startDefaultOn: 4444) > >> onRequestRespond: [ :request | ZnResponse ok: (ZnEntity text: > 'hello') ] > >> > >> In bash: > >> > >> $ lsof -Pi | grep Pharo > >> Pharo 2718 luc 7u IPv4 0x1e64a2e9381f409b 0t0 TCP *:4444 > (LISTEN) > >> > >> I perfectly listen on port 4444 from all interfaces * > >> > >> $ curl http://127.0.0.1:4444 > >> hello > >> > >> $ curl http://localhost:4444 > >> curl: (7) Failed to connect to localhost port 4444: Connection refused > <- why ? > >> > >> localhost is correctly resolved on my mac > >> $ ping localhost > >> PING localhost (127.0.0.1): 56 data bytes > >> 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.044 ms > >> > >> I tested with other programs than Zinc to open listening sockets and it > works. > >> > >> Any idea? > >> > >> #Luc > > maybe http://sourceforge.net/p/curl/bugs/1337/ > > > > Humm, I use curl 7.36.0, so yes perhaps this bug fix is not integrated... > > > > Anyway, I was also suspecting curl but I tested with server: Apache on > port 8888 and here curl works: > > > > httpd 621 luc 5u IPv6 0x6ea19c1d988f10db 0t0 TCP *:8888 > <-- same as Zinc > > > > but both: > > > > curl http://127.0.0.1:8888 > > curl http://localhost:8888 > > > > are working. > > > > wget always works (Apache and Zinc): > > > > wget -qO- http://127.0.0.1:8888 > > wget -qO- http://localhost:8888 > > > > Thanks Max and Ben, > > > > Luc > > > > >

June 14, 2014

Desktop deployment

by Noury Bouraqadi

Hi, In the chapter on desktop deployment [1], what do the installers do? I'm more specifically interested in the Mac OS one. I guess it builds a .dmg file. What should I provide as input ? [1] https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… Thanks Noury -- http://twitter.com/#!/NouryBouraqadi http://car.mines-douai.fr/noury

June 14, 2014

Re: [Pharo-dev] strange difference between localhost and 127.0.0.1 with a Zinc server on mac

by Sven Van Caekenberghe

Luc, I have seen this kind of weirdness before, but I mostly see it with ab (apache benchmark tool). I really have no idea. Have you tried with telnet to do a manual HTTP request ? $ telnet localhost 1701 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. GET /random HTTP/1.1 Host:localhost:1701 HTTP/1.1 200 OK Content-Type: text/plain;charset=utf-8 Content-Length: 64 Date: Sat, 14 Jun 2014 08:58:48 GMT Server: Zinc HTTP Components 1.0 EF97C091498F3FEA3F79F65D36C40ECAFD116A68BA31F45D027DB61EBDD1579 ^] telnet> close Connection closed. You could also try using the same or a second Pharo image to do the request. $ ./pharo Pharo.image eval "ZnClient new get: 'http://localhost:8080/random'" '766EF4E6E5664EF4C5163D30125B5C35BFE2AED408835CB6D6206DF0A7A15FD ' In any case, the server socket used is normally listening on all interfaces [0.0.0.0] Sven On 14 Jun 2014, at 09:17, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: > > > 2014-06-14 6:04 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > Luc Fabresse wrote: >> Hi, >> >> I experiencing a strange difference between localhost and 127.0.0.1. >> >> In Pharo I do: >> >> (ZnServer startDefaultOn: 4444) >> onRequestRespond: [ :request | ZnResponse ok: (ZnEntity text: 'hello') ] >> >> In bash: >> >> $ lsof -Pi | grep Pharo >> Pharo 2718 luc 7u IPv4 0x1e64a2e9381f409b 0t0 TCP *:4444 (LISTEN) >> >> I perfectly listen on port 4444 from all interfaces * >> >> $ curl http://127.0.0.1:4444 >> hello >> >> $ curl http://localhost:4444 >> curl: (7) Failed to connect to localhost port 4444: Connection refused <- why ? >> >> localhost is correctly resolved on my mac >> $ ping localhost >> PING localhost (127.0.0.1): 56 data bytes >> 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.044 ms >> >> I tested with other programs than Zinc to open listening sockets and it works. >> >> Any idea? >> >> #Luc > maybe http://sourceforge.net/p/curl/bugs/1337/ > > Humm, I use curl 7.36.0, so yes perhaps this bug fix is not integrated... > > Anyway, I was also suspecting curl but I tested with server: Apache on port 8888 and here curl works: > > httpd 621 luc 5u IPv6 0x6ea19c1d988f10db 0t0 TCP *:8888 <-- same as Zinc > > but both: > > curl http://127.0.0.1:8888 > curl http://localhost:8888 > > are working. > > wget always works (Apache and Zinc): > > wget -qO- http://127.0.0.1:8888 > wget -qO- http://localhost:8888 > > Thanks Max and Ben, > > Luc >

June 14, 2014

Re: [Pharo-dev] Zinc IPv6 (was Re: strange difference between localhost and 127.0.0.1 with a Zinc server on mac)

by Luc Fabresse

2014-06-14 10:55 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > Luc Fabresse wrote: > > > > 2014-06-14 6:04 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > >> Luc Fabresse wrote: >> >> Hi, >> >> I experiencing a strange difference between localhost and 127.0.0.1. >> >> In Pharo I do: >> >> (ZnServer startDefaultOn: 4444) >> onRequestRespond: [ :request | ZnResponse ok: (ZnEntity text: >> 'hello') ] >> >> In bash: >> >> $ lsof -Pi | grep Pharo >> Pharo 2718 luc 7u IPv4 0x1e64a2e9381f409b 0t0 TCP *:4444 >> (LISTEN) >> >> I perfectly listen on port 4444 from all interfaces * >> >> $ curl http://127.0.0.1:4444 >> hello >> >> $ curl http://localhost:4444 >> curl: (7) Failed to connect to localhost port 4444: Connection refused >> *<- why ?* >> >> localhost is correctly resolved on my mac >> $ ping localhost >> PING localhost (127.0.0.1): 56 data bytes >> 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.044 ms >> >> I tested with other programs than Zinc to open listening sockets and it >> works. >> >> Any idea? >> >> #Luc >> >> maybe http://sourceforge.net/p/curl/bugs/1337/ >> > > Humm, I use curl 7.36.0, so yes perhaps this bug fix is not integrated... > > Anyway, I was also suspecting curl but I tested with server: Apache on > port 8888 and here curl works: > > httpd 621 luc 5u IPv6 0x6ea19c1d988f10db 0t0 TCP *:8888 > <-- same as Zinc > > > Yes. If the *:8888 means that Apache was listening on "all" IP addresses > rather than just 127.0.0.1, then as you can see it was an IPv6 address that > curl connected to. > ah right, I did not read the beginning of the line ;-) So now it is clearer. I conclude that it is a curl bug only for ipv4 > > btw, What do you get from `nslookup localhost` ? > $ nslookup localhost Server: 192.168.0.254 Address: 192.168.0.254#53 Name: localhost Address: 127.0.0.1 > Anyway, the question then becomes... How well does Pharo / Zinc play with > IPv6 ? > the Socket plugin supports some things but I do not remember now. Thx, Luc > > cheers -ben > > > but both: > > curl http://127.0.0.1:8888 > curl http://localhost:8888 > > are working. > > wget always works (Apache and Zinc): > > wget -qO- http://127.0.0.1:8888 > wget -qO- http://localhost:8888 > > Thanks Max and Ben, > > Luc > > >

June 14, 2014

Zinc IPv6 (was Re: strange difference between localhost and 127.0.0.1 with a Zinc server on mac)

by Ben Coman

June 14, 2014

Re: [Pharo-dev] Failing Tests in Pharo 4.0

by Marcus Denker

On 14 Jun 2014, at 04:35, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > In a fresh 4.0 image, I get 10 failures and 11 errors. I guess this is why > the monkey is failing validations... What do we do? > No, it runs the tests twice and just shows the diff. currently failing tests when run headless on the CI server are Zinc.Zodiac.ZnHTTPSTests.testGetPharoVersion 0.398 13 Zinc.Tests.ZnClientTests.testQueryGoogle 0.336 14 Zinc.Resource.Meta.Tests.ZnMimeTypeTests.testLegacy 0.016 19 ReleaseTests.ReleaseTest.testLayoutIntegrity 0.125 21 SlotTests.SlotIntegrationTest.testSlotScopeParallelism 0.123 21 Zinc.Tests.ZnImageExampleDelegateTests.testDefaultImage - of those, all the Zinc onces have been fixed upstream, we need to load the latest zinc in the image. - the slot integrity ones have an issue tracker entry: Failing test: testLayoutIntegrity and testSlotScopeParallelism https://pharo.fogbugz.com/f/cases/13287/ Then there are tests that are failing when running them not on the CI server but in the image headfullâ¦ we should reduce those, too. > What do we do? Just continue what - at least I - do every day? Marcus

June 14, 2014