error 'Network connection closed unexpectedly' while svn update

[Detlef Braungardt]

Hi all,

we use the version 'TortoiseSVN 1.12.2, Build 28653 - 64 Bit , 2019/08/04 13:03:09' of TortoiseSVN.

We are many developers and use a subversion server on an ubuntu 18.04. Subversion on the server has the version '1.9.7-4ubuntu1'.

From time to time we get an error 'Network connection closed unexpectedly' on an update. Not all users get this error.

But after this error, the update is terminated immediately. The next updates are also terminated with the same error.

We are looking for the errors on the server but we did not found an error.

But now I can reproduce this issue with the following steps.

1st step -->

create a small file like 'Test.cpp' with a one line, add and commit this file to subversion server

--

// That is a test for Tortoise

--

2nd step -->

update the directory on an other computer or subversion client to get the first version of 'Test.cpp'

3rd step -->

apply the following patch and commit

--

Index: Test.cpp
===================================================================
--- Test.cpp    (revision 1)
+++ Test.cpp    (revision 2)
@@ -1 +1,2 @@
 // That is a test for Tortoise
+// insert few characters
\ No newline at end of file

--

4th step -->

apply the following patch and commit

--

Index: Test.cpp
===================================================================
--- Test.cpp    (revision 2)
+++ Test.cpp    (revision 3)
@@ -1,2 +1 @@
 // That is a test for Tortoise
-// insert few characters
\ No newline at end of file

--

5th step -->

update the directory again with the other computer or subversion client

now you get the error 'Network connection closed unexpectedly'

In our feeling the root cause is, the second patch revert the changes from the first patch.

If you want to make an update over both versions at the same time then the subversion server combines this two patches and makes a new patch with no changes. Is this new patch a patch with the size of '0'?

We did not get this error with normal source files. But in project files it is possible to undo changes more often.

Is this an error in the settings of TortoiseSVN or is this an bug?

Best regards and thanks in advance for your help.

Detlef Braungardt

[Stefan]

if you can reproduce this with the command line client then you should report this on the subversion mailing list.

However I think you should first check your virus scanner/firewall because such errors are usually caused by those.

[detlef.b...@googlemail.com]

Hi Stefan,

thanks for your reply. I want to answer you ...

No, I cannot reproduce this error with the command line tool. I used for this test a Ubuntu 18.04 with installed subversion in version '1.9.7-4ubuntu1'.

The Ubuntu 18.04 system has the newest updates and so one.

And no, it is not possible, that the error came from the virus scanner or firewall. All other commands (in example commit, log, update) works fine.

And the other point is, I switched off both for a test and I got the same error.

Best regards and thanks in advance for your help

Detlef

---

[Stefan]

On Thursday, October 17, 2019 at 8:11:33 PM UTC+2, (unknown) wrote:

Hi Stefan,

thanks for your reply. I want to answer you ...

No, I cannot reproduce this error with the command line tool. I used for this test a Ubuntu 18.04 with installed subversion in version '1.9.7-4ubuntu1'.

The Ubuntu 18.04 system has the newest updates and so one.

Try to do that on Windows with the CL client that gets installed with TSVN.

 

And no, it is not possible, that the error came from the virus scanner or firewall. All other commands (in example commit, log, update) works fine.

And the other point is, I switched off both for a test and I got the same error.

Depending on your virus scanner: disabling does not really disable it. Most of those 'tools' think that users are stupid and can not be trusted, so they only appear to be disabled...

[detlef.b...@googlemail.com]

Hi Stefan,

thanks for your reply.

I tried this update with the command line of TortoiseSVN now. It is the same error/issue.

Here are the output of the command line:

----

C:\Program Files\TortoiseSVN\bin>svn info "D:\Develop\FIRMA\trunk\Tests"
Path: D:\Develop\FIRMA\trunk\Tests
Working Copy Root Path: D:\Develop\FIRMA
URL: svn+ssh://FIRMA/svn/FIRMA/Projects/trunk/Tests
Relative URL: ^/trunk/Tests
Repository Root: svn+ssh://FIRMA/svn/FIRMA/Projects
Repository UUID: 0713f633-c225-0410-93a4-f350c98dfd2f
Revision: 15747
Node Kind: directory
Schedule: normal
Last Changed Author: detlef
Last Changed Rev: 15747
Last Changed Date: 2019-10-16 07:58:16 +0200 (Mi, 16 Okt 2019)


C:\Program Files\TortoiseSVN\bin>svn update "D:\Develop\FIRMA\trunk\Tests" -r 15749
Updating 'D:\Develop\FIRMA\trunk\Tests':
svn: E235000: In file '/build/subversion-Lv3Qkk/subversion-1.9.7/subversion/libsvn_fs_base/trail.c' line 97: assertion failed (! bfd->in_txn_trail)
svn: E210002: Network connection closed unexpectedly

C:\Program Files\TortoiseSVN\bin>svn update "D:\Develop\FIRMA\trunk\Tests" -r 15748
Updating 'D:\Develop\FIRMA\trunk\Tests':
U    D:\Develop\FIRMA\trunk\Tests\Test.Tortoise\Test.cpp
Updated to revision 15748.

C:\Program Files\TortoiseSVN\bin>svn update "D:\Develop\FIRMA\trunk\Tests" -r 15749
Updating 'D:\Develop\FIRMA\trunk\Tests':
U    D:\Develop\FIRMA\trunk\Tests\Test.Tortoise\Test.cpp
Updated to revision 15749.

C:\Program Files\TortoiseSVN\bin>

---

At the beginning I get the information about the revision. It is 15747.

The revision 15748 is the first change of the file.

And the revision 15749 is the second change of the file and the binary result is the same file as at revision 15747.

With the next update I want to update to revision 15749.

I get the error 'Network connection closed unexpectedly'.

And on the next two updates I go over the revisions step by step. At first to revision 15748 and then 15749.

If I do this step by step I did not get the error and it works.

Best regards and thanks in advance for your help

Detlef

---

[Stefan]

Since you can reproduce the problem with the command line client, please report this on the Subversion users list because the bug/problem is clearly in the svn library and therefore something for the svn developers to fix.

http://subversion.apache.org/mailing-lists.html