svn issues

I'm getting a lot of errors from svn like this:

svn: REPORT request failed on '/svn/llvm-project/!svn/vcc/default'
svn: REPORT of '/svn/llvm-project/!svn/vcc/default': Could not read response
body: Secure connection truncated (https://llvm.org)

I've now been checking out llvm-gcc for two days.

Is there a problem with the server? I don't have this issue with other
svn repositories.

                                              -Dave

Hi David,

I'm getting a lot of errors from svn like this:

svn: REPORT request failed on '/svn/llvm-project/!svn/vcc/default'
svn: REPORT of '/svn/llvm-project/!svn/vcc/default': Could not read response
body: Secure connection truncated (https://llvm.org)

What is /svn/llvm-project/!svn/vcc/default ?

I don't think we have a module named "svn", certainly not "!svn". I
don't know why the svn tool would create such a URL. Also, with https
you need a user id and it looks like one isn't being provided from the
URL shown.

I've now been checking out llvm-gcc for two days.

Is there a problem with the server? I don't have this issue with other
svn repositories.

Dozens of people have been using it successfully since early July. There
was a server restart last night but I don't see others complaining about
it and it hasn't affected my ability to use Subversion. Have you read:

http://llvm.org/docs/GettingStarted.html#checkout

?

Reid.

Hi David,

> I'm getting a lot of errors from svn like this:
>
> svn: REPORT request failed on '/svn/llvm-project/!svn/vcc/default'
> svn: REPORT of '/svn/llvm-project/!svn/vcc/default': Could not read
> response body: Secure connection truncated (https://llvm.org)

What is /svn/llvm-project/!svn/vcc/default ?

I was hoping you'd know the answer to that. :-/

It's not any directory in my local space, that's for sure.

I don't think we have a module named "svn", certainly not "!svn". I
don't know why the svn tool would create such a URL. Also, with https
you need a user id and it looks like one isn't being provided from the
URL shown.

No, I'm definitely providing a username.

Dozens of people have been using it successfully since early July. There
was a server restart last night but I don't see others complaining about
it and it hasn't affected my ability to use Subversion. Have you read:

http://llvm.org/docs/GettingStarted.html#checkout

Of course.

Perhaps it's a problem with the subversion client version I'm using: 1.3.1.
I'll try a later version and see if it helps.

                                               -Dave

It should be okay. I use 1.3.2 all the time.

Reid.

I did find this interesting post:

http://svn.haxx.se/users/archive-2006-10/0413.shtml

"This is by design..." Hmm, not very satisfactory.

And it seems others have encountered these strange URLs as well:

http://svn.haxx.se/users/archive-2007-06/0302.shtml

Here's another relevant thread with interesting notes about compression:

http://gallery.menalto.com/node/53820

So it seems a lot of people are talking about it but it appears nowhere
in the svn issue tracker.

                                              -Dave

David,

Did upgrading to a newer version help at all? If so, I'd like to notify
people to stay away from 1.3.1. What's the status?

Reid.

* Reid Spencer:

Hi David,

I'm getting a lot of errors from svn like this:

svn: REPORT request failed on '/svn/llvm-project/!svn/vcc/default'
svn: REPORT of '/svn/llvm-project/!svn/vcc/default': Could not read response
body: Secure connection truncated (https://llvm.org)

What is /svn/llvm-project/!svn/vcc/default ?

AFAIK, this is the path of an internal URL used by
Subversion-over-HTTP (aka WebDAV). It's pretty standard.

Some kind of middlebox/personal firewall might not process REPORT HTTP
methods and terminate the HTTP connection. Such errors are quite
common in the HTTP case, but with HTTPS, it's a bit rare (because
interception is not entirely trivial).

Just got done checking out llvm-gcc-4.0.

It was sort of better. I still got the error, but much less frequently. I
suppose it could just as easily been due to network latency on our end.
So I don't think we have enough data to support a warning.

                                  -Dave