[squeak-dev] source.squeak.org down again

Hi -

Looks like source.squeak.org is down again. The average posting rate
seems to be 2 package versions a day before it goes bonkers. Grrrr....

We really need a reliable solution if we want the trunk to work. I
certainly don't hope that what we see now is peak usage.

Cheers,
   - Andreas

Do we know anything about what's taking it down?




--
Ron

Hi,

On Sat, Sep 5, 2009 at 2:36 AM, Ronald Spengler<[hidden email]> wrote:
> Do we know anything about what's taking it down?

we've had these problems at HPI, and it was tracked down to Socket
code, IIRC. We weren't able to fix it, though. Probably, it's another
problem on another server.

Best,

Michael

On 05.09.2009, at 09:22, Michael Haupt wrote:

> Hi,
>
> On Sat, Sep 5, 2009 at 2:36 AM, Ronald  
> Spengler<[hidden email]> wrote:
>> Do we know anything about what's taking it down?
>
> we've had these problems at HPI, and it was tracked down to Socket
> code, IIRC. We weren't able to fix it, though. Probably, it's another
> problem on another server.


Right now it seems to be the age-old problem of the i/o hanging, as  
soon as I wiggle the mouse in VNC it continues :/

This is a 3.7 image running on a 3.8a-1 VM from 2005. Lots of stuff  
has been fixed in the mean time, but the squeaksource code would have  
to be ported to a current image.

It's available here:

http://www.squeaksource.com/ss.html

and a port to Seaside 2.8 and Magritte appears to be underway here  
(but I don't know when this forked, it might not have the latest  
changes we had in our version):

http://www.squeaksource.com/ss2.html

- Bert -

Bert Freudenberg wrote:
> Right now it seems to be the age-old problem of the i/o hanging, as soon
> as I wiggle the mouse in VNC it continues :/

Could the wiggler-on-duty then please wiggle? I'm trying to process the
eight packages for the closure fixes from Eliot and of course the server
hangs in the middle...

> This is a 3.7 image running on a 3.8a-1 VM from 2005. Lots of stuff has
> been fixed in the mean time, but the squeaksource code would have to be
> ported to a current image.
>
> It's available here:
>
> http://www.squeaksource.com/ss.html

I would've given it a shot but I see no instructions which of the 23
packages are required to load and in which order, no wiki entry, no
configuration. It must be completely obvious... </irony>

Cheers,
   - Andreas

On 06.09.2009, at 06:53, Andreas Raab wrote:

> Bert Freudenberg wrote:
>> Right now it seems to be the age-old problem of the i/o hanging, as  
>> soon as I wiggle the mouse in VNC it continues :/
>
> Could the wiggler-on-duty then please wiggle? I'm trying to process  
> the eight packages for the closure fixes from Eliot and of course  
> the server hangs in the middle...

Worked for me - not sure if anyone wiggled.

>> This is a 3.7 image running on a 3.8a-1 VM from 2005. Lots of stuff  
>> has been fixed in the mean time, but the squeaksource code would  
>> have to be ported to a current image.
>> It's available here:
>> http://www.squeaksource.com/ss.html
>
> I would've given it a shot but I see no instructions which of the 23  
> packages are required to load and in which order, no wiki entry, no  
> configuration. It must be completely obvious... </irony>


We recently moved our stuff to the official repo. Our own repo has  
install instructions in its wiki tab:

http://source.squeak.org/ss.html

- Bert -

Bert Freudenberg wrote:
>> I would've given it a shot but I see no instructions which of the 23
>> packages are required to load and in which order, no wiki entry, no
>> configuration. It must be completely obvious... </irony>
>
> We recently moved our stuff to the official repo. Our own repo has
> install instructions in its wiki tab:
>
> http://source.squeak.org/ss.html

Thanks. I've got SS sort of running in a trunk image now. It needed a
few fixes (mostly extensions to BlockContext moved to BlockClosure). But
now it hangs in rendering the front page in

SSFrame>>renderHeadElementsOn: html
        super renderHeadElementsOn: html.
        html rssLinkWithUrl: self feedUrl title: self repository title.
        html faviconWithUrl: self faviconUrl.


And WAHtmlRenderer does not understand rssLinkWithUrl:title: (the
message isn't implemented anywhere in the system).

Any ideas, anyone?

Cheers,
   - Andreas

Andreas Raab wrote:
> And WAHtmlRenderer does not understand rssLinkWithUrl:title: (the
> message isn't implemented anywhere in the system).

Okay, so I decided to give it a shot and update the packages from
http://squeaksource.com/ss which appears to be the ticket. I have now a
local Squeaksource version running in a trunk image with so far no ill
side effects.

I'd be happy to post the necessary patches as well as a configuration
map if someone tells me where to put it (I have no access to either ss
repository on source.squeak.org or squeaksource.com).

Cheers,
   - Andreas

On 06.09.2009, at 19:35, Andreas Raab wrote:


It's in Seaside2-lr.96.mcz (see squeaksource.com/ss). I just made a  
config map from the running image:

(
dependency ('DynamicBindings' 'DynamicBindings-gk.1'  
'caa412d9-794d-45a4-b651-7808a5cbf6b7')
dependency ('GraphBuilder' 'GraphBuilder-pmm.4' '6514275b-b260-45f6-
b0eb-ba190bfd3b80')
dependency ('GraphViz' 'GraphViz-pmm.43'  
'98bb0150-883b-43a9-9e19-3a0b381c417b')
dependency ('KomHttpServer' 'KomHttpServer-pmm.7' '33842fe3-5b5e-41ad-
ad7f-4e761141cae1')
dependency ('KomServices' 'KomServices-lr.3'  
'fa3dad6c-5743-43d3-800f-082390e88b3b')
dependency ('Mewa' 'Mewa-pmm.16' 'fc43df10-ce99-493d-8855-956f0c12e48e')
dependency ('Monticello' 'Monticello-avi.279' '7b40dfc0-705b-4a88-8f11-
c87aef1846af')
dependency ('MonticelloConfigurations' 'MonticelloConfigurations-bf.
26' '2f3f3776-cbdf-4f62-a39f-551346e69b83')
dependency ('PackageInfo-Base' 'PackageInfo-Base-bf.22' '5f38fe9a-
bcbb-11d9-8c5b-000d93ca8ba0')
dependency ('SMBase' 'SMBase-gk.63' '49bdafd9-5fda-48cb-
bf66-7895780829fb')
dependency ('SMLoader' 'SMLoader-gk.24' 'e9fb904b-6470-4287-a2fd-
b8a803af6ff6')
dependency ('Scheduler' 'Scheduler-jrp.18'  
'94e578e0-1919-8b40-9971-695da11f9834')
dependency ('Seaside2' 'Seaside2-lr.96' 'cf8fa0c4-
faaf-45f4-8f88-9c5a58ec9290')
dependency ('SqueakSource' 'SqueakSource-bf.1042'  
'54ff5d98-43d0-456f-96f7-e96241bbc0e6')
dependency ('TinyWiki' 'TinyWiki-lr.10'  
'214ea296-8307-11d8-9395-000393cfe6c8')
dependency ('VB-Regex' 'VB-Regex-avi.2'  
'507869eb-237d-11d8-96a3-000a95db7844')
dependency ('XML-Parser' 'XML-Parser-mir.9' '83b817db-e1bf-5849-aba6-
b7c5c0d28b74')
)



- Bert -

On 06.09.2009, at 19:58, Andreas Raab wrote:


I just added you as developer on source.squeak.org.

And the squeaksource.com repo is open to anybody.

Has anyone ever migrated a largish source repository to a new image?  
Anything to watch out for?

- Bert -

Bert Freudenberg wrote:
> I just added you as developer on source.squeak.org.

Thanks. If you take a fully updated trunk image, you can load SS using
the SSLoader configuration map on source.squeak.org. Once loaded, you
can launch SS via:

SSRepository classPool at: #Current
        put: SSRepository defaultRepository.
SSRepository classPool at: #Storage
        put: SSRepository defaultStorage.
SSRepository current rootUrl: 'http://localhost:9090/'.
SSRepository startUp.

(btw, where are the mutators for Current/Storage?)

> And the squeaksource.com repo is open to anybody.

Thanks but I don't want to mess things up (i.e., break stuff in 3.7 etc)
in case there are people still interested in it. I feel more comfortable
messing up things at source.squeak.org since we only need to maintain
the version that we're planning to run ;-)

> Has anyone ever migrated a largish source repository to a new image?
> Anything to watch out for?

Since we have so few projects we could just import all the files again.
We did this when we switched to Gemstone at work and it worked all right.

Cheers,
   - Andreas

2009/9/6 Bert Freudenberg <[hidden email]>:
Lots of fun things having to do with object migration. IIRC Timestamp
was particularly nasty.

Cheers
Philippe

On 08.09.2009, at 09:37, Philippe Marschall wrote:


Ah yes, I found the comment in SSStorage. Fortunately none of these  
appear to be necessary in our case, the image is not *that* old :)

Thank you.

- Bert -