On 6/2/2011 9:02 AM, Stefan Küng wrote:
> On 01.06.2011 23:50, Mark Lakata wrote:
> There may or may not be something wrong with our SVN server, but that is
> > besides the point. If I use the Cygwin command line svn client, I am
> > able to get a change list log, with a few random "svn: REPORT of '....'
> > : 200 OK" messages in the mix. I do not know what is causing these
> > messages, but "OK" does not seem like a fault condition.
> It is a fault condition if something else is expected. If you ask
> "what's the time" and someone answers with "OK", you would treat that as
> a wrong answer as well:)
It is a fault condition, to be sure, but the words "OK" usually mean
everything is "OK". It doesn't sound menacing.
> However, if I hover my mouse up and down the list, I can see traces of
>> the log messages flickering on then off. It appears that the OnPaint
>> handler is drawing the correct log entries, but then wipes it all out
>> and replaces it with the "REPORT of" message.
> Just double click on that. Then the error message vanishes and you can
> see the log entries behind it.
>
Double clicking on the "REPORT of" message does not clear it. I tried
clicking it as fast as I could and it would not clear. If it is intended
to be cleared by double clicking, then there should be a message saying
"double click this to clear it".
Interestingly enough, I can right click (blindly on the white area where
the log message should be) and do "copy to clipboard" and then paste
that information into a text file and read it. That's not really
productive though. :)
>> It seems that the fix is to assign the "REPORT of" message to the
>> individual log entry that is causing the "200 OK" message, instead of a
>> global message that replaces all of the log messages.
> It could be a malformed log message. svn clients must follow certain
> rules for those messages. If your client doesn't do that, it's possible
> to get such malformed messages to the server and that breaks showing the
> log. Try finding the log message that's causing the problem and then
> edit it to something correct.
>
It's possible that the log messages are malformed. This repository has
evolved from CVS, and the guys that did the import into SVN must not
have sanitized the log messages.
It's hard to find the log message that is corrupt if you can't even view
the log messages though!
-Mark
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2756140
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-06-02 18:27:38 CEST