#16342 closed defect (irreproducible)
SVN error during cloning core repoitory
| Reported by: | michael2402 | Owned by: | michael2402 |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | unspecified | Version: | |
| Keywords: | Cc: | stoecker, Biswesh |
Description
I just had a video call and we tried to update a svn clone of the plugins repository.
Beside taking ~5 Minutes, there was a problem when fetching the changes of core.
The base error was @W120106: ra_sref: The server sent a truncated HTTP response body@.
I don't have the complete log any more, but from the problem descriptions I found this has to do with a HTTP timeout of the server that is set to a too low value.
Attachments (1)
Change History (9)
by , 7 years ago
| Attachment: | Bildschirmfoto von »2018-05-31 18-36-33«.png added |
|---|
comment:1 by , 7 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → needinfo |
Did it occur just one time or each time?
comment:2 by , 7 years ago
| Cc: | added |
|---|
After the error, the repository was currupt. You needed to do an svn cleanup, but we did not test for the error any more.
We did not test the reproductitivy of this issue, but I don't think it has something to do with the other error Biswesh got in #16346:
We did not test it any more (since an SVN up took ~10 Minutes), but it the error have been related to a slow internet connection and did not happen before.
I'm not really into SVN and the errors that occur there, because SVN is before my time (the time I started university, GIT already replaced it in most places).
@Biswesh: Have you been able to repair it?
comment:3 by , 7 years ago
No I am still getting the same error. Also I had opened up another ticket for this problem .I will close it.
comment:4 by , 7 years ago
You can leave both open for now, since they may not be related.
I think the externals problem is something different form the problem you experienced here when cloning the JOSM core repository.
My guess is that this ticket may be caused by a connection timeout / loss.
The other one seems to be a configuration problem with the external repository.
comment:5 by , 7 years ago
| Resolution: | → irreproducible |
|---|---|
| Status: | needinfo → closed |
If the svn has an error due to slow network connection after the abort do an "svn cleanup" and retry with "svn up" until checkout is complete.
If this isn't a constant error there is nothing to do here.
comment:6 by , 7 years ago
I have been doing svn cleanup and svn up everytime. But no success till now.
comment:7 by , 7 years ago
Then please provide the complete outputs, so we can analyze what happens.
Error message