[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-devel
Subject: Re: Review Request: Ask the user whether to clean DUChain repository
From: David Nolden <zwabel () googlemail ! com>
Date: 2011-03-09 11:10:01
Message-ID: AANLkTimy6F8k5XFFKrXOt7fpjAt46w-rQDeohfA3Ebi0 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
In rare cases, also a technically valid repository can make kdevelop crash,
because it simply preserves the state. There must be a way to reset the
state in case of problems, which the automatic deletion does.
Am 09.03.2011 09:04 schrieb "Esben Mose Hansen" <kde@mosehansen.dk>:
On Tuesday 08 March 2011 23:52:13 Dmitry Risenberg wrote:
> The bigger question - is this code still...
Wouldn't the right way to do that be to introduce some checksums so
that we can actually test if the repository is corrupt? Say, when
updating the repository, it could
1.a. update the repository
1.b at this stage, the repository is uncorrupt.
2. update the checksum
That way, if we unhappily crashed during 1.a, some checksum would
fail and tip KDevelop off.
Of course, that will not work if the cause is that some code is simply
writing nonsense to the repository.
--
kind regards, Esben
--
KDevelop-devel mailing list
KDevelop-devel@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[Attachment #5 (text/html)]
<p>In rare cases, also a technically valid repository can make kdevelop crash, \
because it simply preserves the state. There must be a way to reset the state in case \
of problems, which the automatic deletion does.</p> <p><blockquote type="cite">Am \
09.03.2011 09:04 schrieb "Esben Mose Hansen" <<a \
href="mailto:kde@mosehansen.dk">kde@mosehansen.dk</a>>:<br><br><p><font \
color="#500050">On Tuesday 08 March 2011 23:52:13 Dmitry Risenberg wrote:<br> > \
The bigger question - is this code still...</font></p>Wouldn't the right way to \
do that be to introduce some checksums so<br> that we can actually test if the \
repository is corrupt? Say, when<br> updating the repository, it could<br>
<br>
1.a. update the repository<br>
1.b at this stage, the repository is uncorrupt.<br>
2. update the checksum<br>
<br>
That way, if we unhappily crashed during 1.a, some checksum would<br>
fail and tip KDevelop off.<br>
<br>
Of course, that will not work if the cause is that some code is simply<br>
writing nonsense to the repository.<br>
<br>
--<br>
kind regards, Esben<br>
<font color="#888888"><br>
--<br>
KDevelop-devel mailing list<br>
<a href="mailto:KDevelop-devel@kdevelop.org">KDevelop-devel@kdevelop.org</a><br>
<a href="https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel" \
target="_blank">https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel</a><br>
</font></blockquote></p>
--
KDevelop-devel mailing list
KDevelop-devel@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic