[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: BUG report for Show Log

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Fri, 19 Sep 2008 19:45:39 +0200

lakata wrote:
> [from wikipedia] The HTTP response status code 200 OK is used to
> represent a successful response from the server, as defined in RFC
> 2616

I know what the response "200 OK" means. But it is completely irrelevant.

If I ask you "what's your name" and you answer "I'm ok", then my
operation (asking you your name) failed because I didn't get the right
answer. You can tell me that you're ok if you want, but it's still not
what you should have said.

It's the same here: the client asks for the log, and the server instead
of providing the log info just tells the client that it's ok. So what
should the client do? Guess what the log is?
No, the client does the right thing: it tells you that an error
happened, and it tells you what the server response was. Sure, it could
also tell you what it would have expected instead of the "200 OK", but
that wouldn't help you. The important info already is in the error
message: the response from the server.

As I said before: contact your hosting company and complain there.

> Also, TSVN should not display the log entries twice.

That's true, and I will look into this. But this won't solve your issue.

> It is possible that this issue is triggered by a server issue, but
> TSVN is not gracefully handling it. It should not say that "200 OK" is
> an error, nor should it list the log entries twice. What do I tell my
> hosting company? "Your server is returning successful responses" ?

Yes, tell them that. Even better, tell them the error the Subversion
client shows you. I've explained above that even if the server returns
"200 OK", it still is an error.

> Don't get me wrong, I think TSVN is a great piece of software and I'm
> grateful for it. The reason for this post is that I need to run
> "blame" on my source code and it isn't working and I don't know how to
> fix it.

If you want blame to work again, you can (until your hoster fixes the
problem) check the "use text viewer" box in the blame dialog: that will
run blame without fetching the log.

Also, the double log entries could be because your hoster uses the same
uuid for all repositories (it wouldn't be the first one doing this
wrong). When you contact your hoster, also point them to this:


  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net

Received on 2008-09-19 19:46:07 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.