[Pharo-dev] Don't do this X(

phil at highoctane.be phil at highoctane.be
Wed Apr 2 10:33:35 EDT 2014


On Wed, Apr 2, 2014 at 4:06 PM, Goubier Thierry <thierry.goubier at cea.fr>wrote:

>
>
> Le 02/04/2014 15:59, Sebastian Sastre a écrit :
>
>> Advice:
>>
>> Never save a "big" package using monticello (lets say ~2000 classes)
>>
>> and then save the image
>>
>> Why?
>>
>> Because while you don't have feedback of saving progress* it will be
>> doing something on background (forked save?) and if for any reason you
>> are tempted to do an image save or save and quit, it will save in a
>> state that will prevent the image from opening again
>>
>> You have no option but to go to your previous image version or something
>> of the kind
>>
>> :(
>>
>> *saving a package actually provides /some/ feedback on progress but when
>> the progress bar finishes, the saving doesn't actually finish and it
>> still have something going on, so you get "silence" (no-feedback) until
>> you get the little monticello window with your new package version
>>
>
> Does this mean that once we get the little window, we are safe?
I am saving a package with containing a lot of Pack-XXX Pack-YYY Pack-ZZZ
in a 2.0 image as a single Pack-PhilippeBack-nn.mcz thing.

What is the moves to make to be safe?

I already got my image locked at some points in a way that resembles what
you describe.

Phil


> I'll profile that to see what's happening.
>
> Thierry
> --
> Thierry Goubier
> CEA list
> Laboratoire des Fondations des Systèmes Temps Réel Embarqués
> 91191 Gif sur Yvette Cedex
> France
> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20140402/71adaaec/attachment-0002.html>


More information about the Pharo-dev mailing list