Error when 'Loading 11313-Pha-CleaningCompilerTests...'

http://code.google.com/p/pharo/issues/detail?id=2327 :
Pharo image: core
Pharo core version: PharoCore1.1ALPHA #11312
Virtual machine used: Squeak 4.2.4beta1U (Mac)
Class browser used if applicable:  Browser

Steps to reproduce:
1. Click System->Software Update

'Error: can''t find EOCD position'

Hi, I think this is a common error caused by corrupt mcz files. Can
you clear your cache and try again?

thanks,
Mike

On Mon, Apr 19, 2010 at 6:47 PM, Sean P. DeNigris <[hidden email]> wrote:
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

> Hi, I think this is a common error caused by corrupt mcz files. Can
> you clear your cache and try again?
Sure, how do I clear the cache?  Also, it was a totally fresh image downloaded from the site.

Sean DeNigris

there is a directory package-cache in the same level that the image
lives. are you doing this in the 1-click image or a normal image?
assuming you can easily see the directory you can just delete it. I'm
sorry i'm not more specific about the error. I'm hoping someone else
chips in with a better description. Last time I debugged one I found
it was an error in the zip protocol; i have no idea why.

cheers,
Mike

2010/4/19 Sean P. DeNigris <[hidden email]>:
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

On Apr 19, 2010, at 10:33 PM, Sean P. DeNigris wrote:

> > Hi, I think this is a common error caused by corrupt mcz files. Can
> > you clear your cache and try again?
> Sure, how do I clear the cache?  Also, it was a totally fresh image downloaded from the site.

on which system are you?
Do you use a one click image

if you use a normal single image not one click, when you download a package it is saved in the folder call
package cache that is created on the side of your image.
throw it away.
Normally the file on the server are not corrupted. We test them before announcing a new release.


Stef

>
> Sean DeNigris
>
> View this message in context: Re: Error when 'Loading 11313-Pha-CleaningCompilerTests...'
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Stéphane Ducasse wrote

on which system are you?
Do you use a one click image

Pharo image: core
Pharo core version: PharoCore1.1ALPHA #11312
Virtual machine used: Squeak 4.2.4beta1U (Mac)

- Sean

  On 19.04.2010 22:56, Sean P. DeNigris wrote: Same error message just popped up for me when I was downloading 11311.
I hit debug, inspected the stream, lo and behold, in the collection I have:
*snip*
"SqueakSource is currently down. We are sorry for the inconvenience and
         working on the problem. In the meantime you can still commit to a
         directory repository on your disk and later copy the versions to
         SqueakSource."
*snip*

So my guess is this is the message you get when it tries to parse the
html error document as a mcz zip archive ;)

Cheers,
Henry

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Henrik Johansen wrote

"SqueakSource is currently down. We are sorry for the inconvenience and
         working on the problem. In the meantime you can still commit to a
         directory repository on your disk and later copy the versions to
         SqueakSource."

Oh, thanks.  I didn't do too much investigating, lol.  

And, maybe the error message could be better than 'Error: can''t find EOCD position.'

Sean

On Apr 21, 2010, at 6:44 05PM, Sean P. DeNigris wrote:


Well... I'm not a network specialist, but the following code looks kind of shady:

HTTPSocket class >> httpGetDocument: url args: args accept: mimeType request: requestString
*snip*
"a 400-series error"
                        sock responseCode first = $4 ifTrue: [^ header, aStream contents].


No idea how much existing code will break if you, say, raise an Exception there instead :)

Cheers,
Henry
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project