On 31/05/2008, MinuteElectron <minuteelectron(a)googlemail.com> wrote:
Anthony wrote:
Asking other people to do your job isn't.
This is actually quite rude when you consider the amount of work that
the employed development team have to do, there are currently only two
paid developers.
Agreed.
You are suggesting that the CTO spend valuable time
programming an
aesthetic change that would not have any considerable benefit
whatsoever, this makes little sense and would only serve to lengthen the
time that other projects -- perhaps more desired by the community --
take to surface.
Strongly disagree. Doing dumps in the right order is not aesthetic and
would have considerable benefit. Perhaps you've misunderstood the
issue?
I've taken a look at the code, and it's a little beyond me to fix, I
think (for a start, it's in Python, which I don't really know), but it
seems the problem is that the failed dumps aren't being deleted. When
the code looks to see when the latest dump was it does so by looking
in the dump directory and seeing what the latest dump in there is, if
the failed ones were deleted as soon as it's realised they've failed,
the problem with the order would be fixed (and it would free up disc
space). There may be parts of the failed dump that have succeeded and
it may seem wasteful to just delete them, but, as I understand it, the
whole dump has to be redone to redo the failed parts, and if the whole
lot is deleted it will be redone almost straight away, so there's only
going to be a few hours in which the deleted dump may have been
useful.