[squeak-dev] Squeaksource data loss?

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

[squeak-dev] Squeaksource data loss?

Andreas.Raab
Folks -

I'm not sure who to direct this to, but it looks like I just lost some
important data on squeaksource.com. For testing the closure bootstrap, I
had added various configuration maps to the MCUpdateTests repository. As
of these morning these version seem to have gone; as a consequence, the
closure bootstrap breaks instantly.

It is very disturbing to me that such a valuable community service would
suffer data loss. Does anyone know who to contact regarding the matter?

Thanks,
   - Andreas

Reply | Threaded
Open this post in threaded view
|

Re: [squeak-dev] Squeaksource data loss?

Lukas Renggli
Squeaksource crashed yesterday and I had to restart it. Unfortunately
MCM files are not stored on the filesystem (support was added later
and does not cleanly integrate into the persistency system), and thus
are not persistent after a crash.

Lukas

On Saturday, July 18, 2009, Andreas Raab <[hidden email]> wrote:

> Folks -
>
> I'm not sure who to direct this to, but it looks like I just lost some important data on squeaksource.com. For testing the closure bootstrap, I had added various configuration maps to the MCUpdateTests repository. As of these morning these version seem to have gone; as a consequence, the closure bootstrap breaks instantly.
>
> It is very disturbing to me that such a valuable community service would suffer data loss. Does anyone know who to contact regarding the matter?
>
> Thanks,
>   - Andreas
>
>

--
Lukas Renggli
http://www.lukas-renggli.ch

Reply | Threaded
Open this post in threaded view
|

[squeak-dev] Re: Squeaksource data loss?

Andreas.Raab
Lukas Renggli wrote:
> Squeaksource crashed yesterday and I had to restart it. Unfortunately
> MCM files are not stored on the filesystem (support was added later
> and does not cleanly integrate into the persistency system), and thus
> are not persistent after a crash.

Thanks. I'm obviously quite upset about the data loss. I know this will
sound heretical, but in my experience Gemstone is a much superior
solution for anything that runs at that scale. Given the importance of
this service for the community, perhaps we should consider doing
something undogmatic occasionally?

Cheers,
   - Andreas