It turned out that the problem appeared randomly on various configurations and the cause is possibly a low memory condition.
Also possible is an instable smalltalkhub.
The problems were blocking us for a while with no clear cause. That is quite annoying.
Phil
Hi Phil,
��
nothing I can reproduce here. I tried with the latest/fresh
Pharo 3.0 (build 30858) image. No problem to load from script or config browser.
Also CI is green.
Are you already using Pharo 4.0? Then it might be related that
the prerequisite Seaside version may be not yet be ready/supported
for Pharo 4.0.
https://ci.inria.fr/pharo-contribution/job/Pharo4Seaside/
Bye
T.