When I commit large changes - hundreds of megabytes - the client timesout even though the check-in does go through.
When I right-click on WC and show log, TSVN shows that WC revision does NOT get updated even though the check-in actually occurred.
I've tried using TortoiseSVN 1.9.5, Build 27581 - 64 Bit
and command line svn version 1.9.5 (r1770682)
.
QUESTION
Is there a way to increase the timeout of the client?
If you are using HTTP to connect to the server (as it appears to be the case) you can increase (or disable) the time out with the http-timeout
directive, as explained at Runtime Configuration Area:
http-timeout
This specifies the amount of time, in seconds, to wait for a server response. If you experience problems with a slow network connection causing Subversion operations to time out, you should increase the value of this option. In Subversion 1.8 (or older versions employing the Serf-based HTTP provider), use the value 0 to disable the timeout altogether.
Just make sure you aren't merely masking a problem (it's strange that commit completes successfully but server response doesn't make through).
来源:https://stackoverflow.com/questions/42861248/svn-client-timing-out-and-corrupting-wc-state