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

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

new Cog VMs available

by Eliot Miranda

...in http://www.mirandabanda.org/files/Cog/VM/VM.r3000/ CogVM binaries as per VMMaker.oscog-eem.772/r3000 Add libcrypto and libssl to Linux and Mac builds of the SqueakSSL plugin. Add the XDisplayControlPlugin and include it (external) and the AioPlugin (internal) to the linux x86 builds. Cog: Fix an abort (relocating call to invalid address) due to an over-zealous check in relocateCallBeforeReturnPC:by:. Since we relocate e.g. calls to primitives there can be no effective range check there-in. Spur: Fix fillObj: signedness for objects straddling the midpoint of the address space (quickly affects linux). Similarly for routines in pigCompact, to get asserts correct. Fix printOopsFrom:to:. for objects up to endOfMemory. Declare lastFreeChunk and firstFreeChunk correctly. Fix numberOfForwarders: and printForwarders: for isForwarded:'s blindness towards freeChunks. Comment isForwarded: to be clear on the issue. Have the segment manager pass to sqAllocateMemorySegmentOfSize: the address of the first large enough gap in the address space, instead of the address of the end of the first segment. This allows e.g. linux to use MAP_FIXED and hence get past a 128Mb limit on mmapping. Fix bugs in isValidFreeObject: & printFreeTreeChunk: that caused bogus assert failures. Remember to include the Spur moniker in the -version output on linux -- best, Eliot

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] [squeak-dev] New Cog & Spur VMs available

by Eliot Miranda

Hi StÃ©ph, On Fri, Jun 13, 2014 at 4:38 AM, StÃ©phane Rollandin <lecteur(a)zogotounga.net> wrote: > I got a crash right away with newest cogwin when opening my usual working > image. No simple case easy to reproduce yet. Dump is attached. > Thanks. This is fixed in VMMaker.oscog-eem.772. It was an overzealous bounds check on a relocated call of an interpreter primitive. The VM complained and aborted because the interpreter primitive;s address was out of the code zone (as of course it should be; it is in the interpreter) i.e. the VM should not have performed the check and should not have exited. Apologies. I'll be building and uploading new VMs soon. -- best, Eliot

June 14, 2014

Failing Tests in Pharo 4.0

by Sean P. DeNigris

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? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Failing-Tests-in-Pharo-4-0-tp4763069.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 14, 2014

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

by Max Leske

Canât reproduce (OSX 10.9.3). Both curl calls work perfectly for me. Maybe its your curl? Max On 13.06.2014, at 21:32, Luc Fabresse <luc.fabresse(a)gmail.com> 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

June 13, 2014

Re: [Pharo-dev] issue validation needed

by Max Leske

Tested in 30 and 40 with normal configurations. Somebody who is using FileTree should test Git configurations. Max On 07.06.2014, at 15:50, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > this is a problem that arises with the ConfigurationOfCog (changed to use VMMaker.oscog, instead VMMaker-oscog). > is hard to reproduce because I spotted it in a weird combination: is a configuration that uses just the baseline and files are in filetree format. > > to reproduce it, save a package as a branch (for example, save package A as A.branch-YourName.1) > then change a configuration: > > package: âA.branchâ > > then you will see an error. > but most important to me is to check that this change does not forbids other configurations to load. > also I will need to backport it to 3.0 because this is needed for building the vm :( > > yes, I could rename the package again and use it like before, but I wanted to align as close as possible to current Eliot sources. > > cheers, > Esteban > > On 05 Jun 2014, at 14:49, Max Leske <maxleske(a)gmail.com> wrote: > >> Is there an easy way to reproduce this? I donât quite see what I have to do to verify the fix. >> >> >>> On 05.06.2014, at 14:30, Damien Cassou <damien.cassou(a)gmail.com> wrote: >>> >>> On Wed, Jun 4, 2014 at 9:12 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> can someone check this metacello issue? >>>> >>>> https://pharo.fogbugz.com/f/cases/13305/ >>>> >>>> I really need it for continue with VM work. >>> >>> >>> for the laziest among you: >>> >>> Problem resolving branches with Metacello >>> The fix is in the Inbox >>> >>> >>> -- >>> Damien Cassou >>> http://damiencassou.seasidehosting.st >>> >>> "Success is the ability to go from one failure to another without >>> losing enthusiasm." >>> Winston Churchill >>> >> >> > >

June 13, 2014

strange difference between localhost and 127.0.0.1 with a Zinc server on mac

by Luc Fabresse

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

June 13, 2014

Re: [Pharo-dev] Improving Pharo By Example

by Gabriel Cotelli

Yes.. I usually remove the previous content before using the zero conf script.. (I'm not using pillar but the basic script don't work if you already have the vm and tries to download it again, at least on my Linux box). Hope it helps On Fri, Jun 13, 2014 at 2:25 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > what "clean the directory" mean ? And how I do that ? Do I need to delete > the directory and reclone it ? > > > On Fri, Jun 13, 2014 at 7:57 PM, Gabriel Cotelli <g.cotelli(a)gmail.com> > wrote: > >> Clean the directory where you're running the script. If some of the files >> already exists the zero conf script won't work. >> >> >> On Fri, Jun 13, 2014 at 12:14 PM, kilon alios <kilon.alios(a)gmail.com> >> wrote: >> >>> thanks Damien that works. >>> >>> However running ./update.sh afterwards creates this error >>> >>> "2014-06-13 18:07:52 (1,01 MB/s) - written to stdout [5311/5311] >>> >>> Downloading the latest pharoVM: >>> http://files.pharo.org/vm/pharo/linux/stable.zip >>> mkdir: cannot create directory âpharo-vmâ: File exists >>> " >>> >>> is this normal ? >>> >>> >>> On Fri, Jun 13, 2014 at 5:17 PM, Damien Cassou <damien.cassou(a)gmail.com> >>> wrote: >>> >>>> On Fri, Jun 13, 2014 at 2:00 PM, kilon alios <kilon.alios(a)gmail.com> >>>> wrote: >>>> > So how I proceed ? >>>> >>>> >>>> the Ubuntu PPA is made for this: >>>> >>>> sudo add-apt-repository ppa:pharo/stable >>>> sudo apt-get update >>>> sudo apt-get install pharo-launcher >>>> >>>> Can't be more simple than that >>>> >>>> >>>> >>>> -- >>>> Damien Cassou >>>> http://damiencassou.seasidehosting.st >>>> >>>> "Success is the ability to go from one failure to another without >>>> losing enthusiasm." >>>> Winston Churchill >>>> >>>> >>> >> >

June 13, 2014

Re: [Pharo-dev] Improving Pharo By Example

by kilon alios

what "clean the directory" mean ? And how I do that ? Do I need to delete the directory and reclone it ? On Fri, Jun 13, 2014 at 7:57 PM, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > Clean the directory where you're running the script. If some of the files > already exists the zero conf script won't work. > > > On Fri, Jun 13, 2014 at 12:14 PM, kilon alios <kilon.alios(a)gmail.com> > wrote: > >> thanks Damien that works. >> >> However running ./update.sh afterwards creates this error >> >> "2014-06-13 18:07:52 (1,01 MB/s) - written to stdout [5311/5311] >> >> Downloading the latest pharoVM: >> http://files.pharo.org/vm/pharo/linux/stable.zip >> mkdir: cannot create directory âpharo-vmâ: File exists >> " >> >> is this normal ? >> >> >> On Fri, Jun 13, 2014 at 5:17 PM, Damien Cassou <damien.cassou(a)gmail.com> >> wrote: >> >>> On Fri, Jun 13, 2014 at 2:00 PM, kilon alios <kilon.alios(a)gmail.com> >>> wrote: >>> > So how I proceed ? >>> >>> >>> the Ubuntu PPA is made for this: >>> >>> sudo add-apt-repository ppa:pharo/stable >>> sudo apt-get update >>> sudo apt-get install pharo-launcher >>> >>> Can't be more simple than that >>> >>> >>> >>> -- >>> Damien Cassou >>> http://damiencassou.seasidehosting.st >>> >>> "Success is the ability to go from one failure to another without >>> losing enthusiasm." >>> Winston Churchill >>> >>> >> >

June 13, 2014