svn 客户端超时并破坏 WC 状态 [英] svn client timing out and corrupting WC state

查看:79
本文介绍了svn 客户端超时并破坏 WC 状态的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

当我提交大量更改(数百兆字节)时,即使签入确实通过,客户端也会超时.

When I commit large changes - hundreds of megabytes - the client timesout even though the check-in does go through.

当我右键单击 WC 并显示日志时,TSVN 显示即使签入实际发生,WC 修订版也未更新.

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.

我尝试使用 TortoiseSVN 1.9.5, Build 27581 - 64 Bit 和命令行 svn version 1.9.5 (r1770682).

I've tried using TortoiseSVN 1.9.5, Build 27581 - 64 Bit and command line svn version 1.9.5 (r1770682).

问题

有没有办法增加客户端的超时时间?

Is there a way to increase the timeout of the client?

推荐答案

如果您使用 HTTP 连接到服务器(看起来就是这种情况),您可以使用 http-timeout 指令,如 运行时配置所述区域:

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 超时

这指定了等待服务器响应的时间量(以秒为单位).如果您遇到网络缓慢的问题连接导致 Subversion 操作超时,您应该增加此选项的值.在 Subversion 1.8(或更旧的使用基于 Serf 的 HTTP 提供程序的版本),使用值 0完全禁用超时.

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).

这篇关于svn 客户端超时并破坏 WC 状态的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆