Thank you! Vincent
From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of Vitor Medina Cruz Sent: Tuesday, June 19, 2018 12:10 To: Any question about pharo is welcome <pharo-users@lists.pharo.org> Subject: Re: [Pharo-users] Pharo 7 proxy problem Done! https://pharo.fogbugz.com/f/cases/22177/Pharo-7-proxy-problem<https://urldefense.proofpoint.com/v2/url?u=https-3A__pharo.fogbugz.com_f_cases_22177_Pharo-2D7-2Dproxy-2Dproblem&d=DwMFaQ&c=RWI7EqL8K9lqtga8KxgfzvOYoob76EZWE0yAO85PVMQ&r=kIZIYXBAA3fhM7P5HOuTC5w6mnEApTfXPTq3lR34ZiY&m=ojh_GCqou63NvJlpqOGtEo_6tXLMPvGETlzUJmpMe-E&s=WL8ShrQQ6J2V0NjznQYdUC1BCi7aosvQ2I8vBRa8cFM&e=> On Tue, Jun 19, 2018 at 3:55 PM, <vincent.blond...@lamresearch.com<mailto:vincent.blond...@lamresearch.com>> wrote: Great! Could you create a bug report with the stack trace here: https://pharo.fogbugz.com/f/cases/new<https://urldefense.proofpoint.com/v2/url?u=https-3A__pharo.fogbugz.com_f_cases_new&d=DwMFaQ&c=RWI7EqL8K9lqtga8KxgfzvOYoob76EZWE0yAO85PVMQ&r=kIZIYXBAA3fhM7P5HOuTC5w6mnEApTfXPTq3lR34ZiY&m=ojh_GCqou63NvJlpqOGtEo_6tXLMPvGETlzUJmpMe-E&s=fd8CawAlLJ8LCtj8IXRxaZuNu_BWIC6f0NXzu1S5SNM&e=> ? It should be an issue with the socket library under x64. Drag and drop the file into the image ;) However the classes should be the same, otherwise you’ll get an error. That’s why I asked the version Cheers, Vincent From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org<mailto:pharo-users-boun...@lists.pharo.org>] On Behalf Of Vitor Medina Cruz Sent: Tuesday, June 19, 2018 11:46 To: Any question about pharo is welcome <pharo-users@lists.pharo.org<mailto:pharo-users@lists.pharo.org>> Subject: Re: [Pharo-users] Pharo 7 proxy problem Oh! on 32 bits version worked \o/, just tested it now. On Tue, Jun 19, 2018 at 3:43 PM, Vitor Medina Cruz <vitormc...@gmail.com<mailto:vitormc...@gmail.com>> wrote: I just download it using Pharo Launcher [cid:image001.png@01D407CB.F6D840B0] Out of curiosity, how do I deserialize it into an image? :) On Tue, Jun 19, 2018 at 3:36 PM, <vincent.blond...@lamresearch.com<mailto:vincent.blond...@lamresearch.com>> wrote: Hi, Could you send the serialized stack of your primitive failure? [cid:image002.png@01D407CB.F6D840B0] And the version of Pharo you are using? Thanks, Vincent Blondeau From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org<mailto:pharo-users-boun...@lists.pharo.org>] On Behalf Of Vitor Medina Cruz Sent: Tuesday, June 19, 2018 11:30 To: Any question about pharo is welcome <pharo-users@lists.pharo.org<mailto:pharo-users@lists.pharo.org>> Subject: Re: [Pharo-users] Pharo 7 proxy problem Yes, it can resolve. On Tue, Jun 19, 2018 at 1:30 PM, Esteban Lorenzano <esteba...@gmail.com<mailto:esteba...@gmail.com>> wrote: have you tested your windows can resolve localhost? I’m not a regular windows user, but I remember time ago this was not evident on windows systems. Esteban > On 19 Jun 2018, at 18:23, Vitor Medina Cruz > <vitormc...@gmail.com<mailto:vitormc...@gmail.com>> wrote: > > Hello, > > I decided to give a try on Pharo 7 and see how iceberg is doing.... on > windows :) > > Pharo launcher is working fine by the way — I had some problems with it in > the past, but it seems more stable now. > > Well, if using windows isn't bad enought I am behind a proxy, so I use cntlm > and my configuration in Pharo 6.1 for cntlm proxy on localhost works fine, > but in 7 don't. First it seems to not recognize localhost as 127.0.0.1, it > prompts the message: NameLookupFailure: cannot resolve 'localhost' > > Using 127.0.0.1 I got a PrimitiveFailure (Ick!): > > PrimitiveFailed: primitive > #primSocketCreateNetwork:type:receiveBufferSize:sendBufSize:semaIndex:readSemaIndex:writeSemaIndex: > in Socket failed' > > Since it is a primitive problem, I figure there is no workaround possible > here... right? > > > ------------------------------------------------ > > > Socket(ProtoObject)>>primitiveFailed: > Socket(ProtoObject)>>primitiveFailed > Socket>>primSocketCreateNetwork:type:receiveBufferSize:sendBufSize:semaIndex:readSemaIndex:writeSemaIndex: > Socket>>initialize: > [ super new initialize: TCPSocketType ] in Socket class>>newTCP in Block: [ > super new initialize: TCPSocketType ] > BlockClosure>>repeatWithGCIf: > Socket class>>newTCP > ZdcSocketStream class(ZdcSimpleSocketStream > class)>>openConnectionToHost:port:timeout: > ZnNetworkingUtils>>socketStreamToUrlDirectly: > ZnNetworkingUtils>>socketStreamToProxy > ZnNetworkingUtils>>socketStreamToUrl: > ZnNetworkingUtils class>>socketStreamToUrl: > ZnClient>>newConnectionTo: > ZnClient>>getConnectionAndExecute > ZnClient>>executeWithRedirectsRemaining: > [ self executeWithRedirectsRemaining: self maxNumberOfRedirects ] in > ZnClient>>executeWithRetriesRemaining: in Block: [ self > executeWithRedirectsRemaining: self maxNumb...etc... > BlockClosure>>on:do: > ZnClient>>executeWithRetriesRemaining: > [ self executeWithRetriesRemaining: self numberOfRetries ] in [ [ self > executeWithRetriesRemaining: self numberOfRetries ] > on: Error > do: self ifFailBlock ] in ZnClient>>executeWithTimeout in Block: [ self > executeWithRetriesRemaining: self numberOfR...etc... > BlockClosure>>on:do: > [ [ self executeWithRetriesRemaining: self numberOfRetries ] > on: Error > do: self ifFailBlock ] in ZnClient>>executeWithTimeout in Block: [ [ self > executeWithRetriesRemaining: self numberO...etc... > [ ^ block value ] in ZnClient>>withTimeoutDo: in Block: [ ^ block value ] > [ activeProcess psValueAt: index put: anObject. > aBlock value ] in ZnConnectionTimeout(DynamicVariable)>>value:during: in > Block: [ activeProcess psValueAt: index put: anObject.... > BlockClosure>>ensure: > ZnConnectionTimeout(DynamicVariable)>>value:during: > ZnConnectionTimeout class(DynamicVariable class)>>value:during: > ZnClient>>withTimeoutDo: > ZnClient>>executeWithTimeout > [ result := self executeWithTimeout ] in ZnClient>>execute in Block: [ result > := self executeWithTimeout ] > [ ^ block value ] in ZnClient>>withProgressDo: in Block: [ ^ block value ] > > Regards, > Vitor
