[BUG]: Zinc-HTTP-SvenVanCaekenberghe.285 GoferRepositoryError

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[BUG]: Zinc-HTTP-SvenVanCaekenberghe.285 GoferRepositoryError

Sean P. DeNigris
Administrator
In the latest Pharo 1.4 (https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/455/artifact/Pharo-1.4.zip)...

1. Download ConfigurationLoadingPhexample.st
2. Evaluate the following:
Gofer it
        url: 'http://mc.stfx.eu/ZincHTTPComponents';
        version: 'Zinc-HTTP-SvenVanCaekenberghe.285';
        load.
'/path/to/ConfigurationLoadingPhexample.st' asFileReference fileStreamDo: [ :str | str fileIn ].
((Smalltalk at: #ConfigurationLoadingPhexample) project version: #'bleedingEdge') load.

You should get: "Error: Could not resolve: ConfigurationOfPhexample [ConfigurationOfPhexample] in /path/to/package-cache http://www.squeaksource.com/MetacelloRepository ERROR: 'GoferRepositoryError: 2'"

If you change the HTTP package line to "version: 'Zinc-HTTP-SvenVanCaekenberghe.284';", it successfully downloads.

n.b. if the package is in your cache, you won't see the error
Cheers,
Sean
Reply | Threaded
Open this post in threaded view
|

Re: [BUG]: Zinc-HTTP-SvenVanCaekenberghe.285 GoferRepositoryError

Sven Van Caekenberghe
Sean,

I took 1.4 #14453 and executed

Gofer it
        url: 'http://mc.stfx.eu/ZincHTTPComponents';
        package: 'Zinc-HTTP';
        package: 'Zinc-FileSystem-Legacy';
        package: 'Zinc-Tests';
        load.

Thus loading the latest versions like Zinc-HTTP-SvenVanCaekenberghe.287

And yes, for some reason the first Zn related operation fails (related to a process local (ZnSignalProgress) var not being there, its an index out of bounds), but if you try again it works. And all tests pass. So its a bit hard to debug.

The latest 2.0 image has the same transient problem ;-)

Sven

On 15 Jul 2012, at 01:51, Sean P. DeNigris wrote:

> In the latest Pharo 1.4
> (https://ci.lille.inria.fr/pharo/view/Pharo%201.4/job/Pharo%201.4/455/artifact/Pharo-1.4.zip)...
>
> 1. Download
> http://forum.world.st/file/n4640031/ConfigurationLoadingPhexample.st
> ConfigurationLoadingPhexample.st
> 2. Evaluate the following:
> Gofer it
> url: 'http://mc.stfx.eu/ZincHTTPComponents';
> version: 'Zinc-HTTP-SvenVanCaekenberghe.285';
> load.
> '/path/to/ConfigurationLoadingPhexample.st' asFileReference fileStreamDo: [
> :str | str fileIn ].
> ((Smalltalk at: #ConfigurationLoadingPhexample) project version:
> #'bleedingEdge') load.
>
> You should get: "Error: Could not resolve: ConfigurationOfPhexample
> [ConfigurationOfPhexample] in /path/to/package-cache
> http://www.squeaksource.com/MetacelloRepository ERROR:
> 'GoferRepositoryError: 2'"
>
> If you change the HTTP package line to "version:
> 'Zinc-HTTP-SvenVanCaekenberghe.284';", it successfully downloads.
>
> n.b. if the package is in your cache, you won't see the error
>
> --
> View this message in context: http://forum.world.st/BUG-Zinc-HTTP-SvenVanCaekenberghe-285-GoferRepositoryError-tp4640031.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
>


Reply | Threaded
Open this post in threaded view
|

Re: [BUG]: Zinc-HTTP-SvenVanCaekenberghe.285 GoferRepositoryError

Sean P. DeNigris
Administrator
On Jul 15, 2012, at 6:45 AM, "Sven Van Caekenberghe [via Smalltalk]" <[hidden email]> wrote:
> for some reason the first Zn related operation fails
Here's another weird bit of info... in the snippet I posted, if I load the http package and the metacello config in two separate doIts, it works. If I try to do both in one doIt, it fails.

btw. Wtf is a "GoferRepositoryError: 2"?!

Thanks for looking into this. The changes between 284 and 285 were so minor, it seems like this should be easier. My totally unsubstantiated hunch... the only thing the signal class was added and we've been working on system change notifications... could that have anything to do with it? The two doIts thing leads me to believe the bug is in the kernel, outside of zinc...

Sean
Cheers,
Sean
Reply | Threaded
Open this post in threaded view
|

Re: [BUG]: Zinc-HTTP-SvenVanCaekenberghe.285 GoferRepositoryError

Camillo Bruni-3

On 2012-07-15, at 17:39, Sean P. DeNigris wrote:

> On Jul 15, 2012, at 6:45 AM, "Sven Van Caekenberghe [via Smalltalk]" <[hidden email]> wrote:
>> for some reason the first Zn related operation fails
> Here's another weird bit of info... in the snippet I posted, if I load the http package and the metacello config in two separate doIts, it works. If I try to do both in one doIt, it fails.
>
> btw. Wtf is a "GoferRepositoryError: 2"?!

Indeed... the Gofer Error could at least wrap around the real cause, makes debugging a nightmare :D

> Thanks for looking into this. The changes between 284 and 285 were so minor, it seems like this should be easier. My totally unsubstantiated hunch... the only thing the signal class was added and we've been working on system change notifications... could that have anything to do with it? The two doIts thing leads me to believe the bug is in the kernel, outside of zinc...
>
> Sean
>
> --
> View this message in context: http://forum.world.st/BUG-Zinc-HTTP-SvenVanCaekenberghe-285-GoferRepositoryError-tp4640031p4640079.html
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.


Reply | Threaded
Open this post in threaded view
|

Re: [BUG]: Zinc-HTTP-SvenVanCaekenberghe.285 GoferRepositoryError

Sean P. DeNigris
Administrator
In reply to this post by Sven Van Caekenberghe
Sven Van Caekenberghe wrote
for some reason the first Zn related operation fails
Found it!
Issue 6376: New ProcessSpecificVariables & Running Processes
http://code.google.com/p/pharo/issues/detail?id=6376
Cheers,
Sean
Reply | Threaded
Open this post in threaded view
|

Re: [BUG]: Zinc-HTTP-SvenVanCaekenberghe.285 GoferRepositoryError

Sean P. DeNigris
Administrator
In reply to this post by Camillo Bruni-3
Camillo Bruni-3 wrote
Indeed... the Gofer Error could at least wrap around the real cause, makes debugging a nightmare :D
Issue 6379: Sensible GoferRepositoryError Messages
http://code.google.com/p/pharo/issues/detail?id=6379
Cheers,
Sean