On Jun 15, 2010, at 9:42 AM, Hernán Morales Durand wrote:
> Why the ancestor chain is broken if the save failed?
>
> Of course if the fix breaks other parts I agree to revert or reopen
> the issue until we find a better solution.
because (may be I'm wrong)
your cache will contain v+1
and when you will republish v+2 its ancestor v+1 will not be saved on the server
so on the server we will get
v and v+2
>
> What people think about triggering specific exceptions for different
> failures? When I saw this issue it seemed to me no trivial to
> implement it to my MC knowledge at least. If nobody take it I will
> have a look tonight, sorry for the unwanted effects just trying to get
> a better Pharo experience.
would be nice to have better exception so that we can react adequately
>
> Hernán
>
> 2010/6/15 Stéphane Ducasse <[email protected]>:
>> It would be nice to fix that in a better way.
>> Hernan we integrated your change but now the package stays dirty and if you
>> republish in the repository
>> then you may break the ancestor chain so I do not know what to do.
>>
>> Stef
>>
>> On Jun 15, 2010, at 7:37 AM, Lukas Renggli wrote:
>>
>>>> This is because "2" should not be created. If a copy cannot be saved
>>>> then there is no reason to increment the version number with the
>>>> failed attempt. May deserve another issue entry?
>>>>
>>>> Please comment I would like to read opinions on this.
>>>
>>> I noticed this problem too. The previous behavior was better, at least
>>> if you knew how to fix you credentials in the debugger.
>>>
>>> Lukas
>>>
>>> --
>>> Lukas Renggli
>>> www.lukas-renggli.ch
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> [email protected]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [email protected]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
