水银& Windows Server 2003
我刚刚在我们的主网络服务器上设置了 Mercurial,通过 hgwebdir.cgi 托管存储库。我现在遇到的问题是,当我从本地计算机运行 hg Push 到服务器的存储库时,推送一个非常小的目录(只有一个变更集)需要花费绝对荒谬的时间。有没有可能是我设置错误了?我不断收到 HTTP 错误 502:网关错误。
I just set up Mercurial on our main webserver, hosting repositories via hgwebdir.cgi. The problem I'm having now is when I run hg push from my local machine to the server's repository, it takes an absolutely ridiculous amount of time to push a very small directory, with only a single changeset. Is it possible that I've set something up wrong? I keep getting HTTP Error 502: Bad Gateway.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
看起来有点像问题 2716,其中建议:
这是一种解决方法对于你遇到的问题,基本上你不需要大力推动,
将其分解为许多较小的推送:
找出存储库的修订数量。
复制并粘贴以下脚本(在 bash 中,如果您不喜欢 bash,请使用您最喜欢的脚本语言):
等待其运行。
如果某些推送失败,请不要担心,以下推送会解决问题。
话虽这么说,Windows IIS 上的问题已也报道了。
此“博客文章评论”还详细介绍了:
Looks a bit like issue 2716 which suggests:
Here's a workaround for the problem you are having, basically instead of doing one huge push, you
break it down into many smaller pushes:
Find out the number of revisions of your repository.
Copy and paste the following script, (in bash, use your favorite scripting language if you don't like bash):
Wait for that to run.
If some of the pushes fail, don't worry, the following push will catch things up.
That being said, issues on Windows IIS has been reported as well.
This "blog post comment" also details: