Mercurial-解决中止的方法:汞柱内/拉入后错误:'' [英] Mercurial - Ways to resolve abort: error: '' after an hg in/pull

问题描述

一个完美的存储库在未知的时间后变成了梨形.
一个简单的 hg输入失败，并显示错误
中止:错误:"

A perfectly good repository goes pear shaped after an unknown time.
A simple hg in fails with an error
abort: error: ''

有时它会挂几分钟，没有任何输出.

Sometimes it just hangs for a few minutes without any output.

如果我运行-verbose ，则输出相同.
如果使用-traceback 运行，则会得到:

If I run with --verbose, same output.
If I run with --traceback, I get:

Traceback (most recent call last):
  File "mercurial\dispatch.pyo", line 88, in _runcatch
  File "mercurial\dispatch.pyo", line 740, in _dispatch
  File "mercurial\dispatch.pyo", line 514, in runcommand
  File "mercurial\dispatch.pyo", line 830, in _runcommand
  File "mercurial\dispatch.pyo", line 801, in checkargs
  File "mercurial\dispatch.pyo", line 737, in <lambda>
  File "mercurial\util.pyo", line 471, in check
  File "mercurial\commands.pyo", line 3901, in incoming
  File "mercurial\hg.pyo", line 513, in incoming
  File "mercurial\hg.pyo", line 472, in _incoming
  File "mercurial\bundlerepo.pyo", line 342, in getremotechanges
  File "mercurial\discovery.pyo", line 45, in findcommonincoming
  File "mercurial\setdiscovery.pyo", line 184, in findcommonheads
  File "mercurial\wireproto.pyo", line 116, in plain
  File "mercurial\wireproto.pyo", line 164, in _submitone
  File "mercurial\httppeer.pyo", line 170, in _call
  File "mercurial\httppeer.pyo", line 118, in _callstream
  File "urllib2.pyo", line 400, in open
  File "urllib2.pyo", line 418, in _open
  File "urllib2.pyo", line 378, in _call_chain
  File "mercurial\url.pyo", line 314, in http_open
  File "mercurial\keepalive.pyo", line 257, in do_open
URLError: <urlopen error ''>
abort: error: ''

没有更多详细信息...
有谁知道如何调试并解决这个问题?我最终再次克隆了父存储库，并删除了旧的存储库:-(

No further details...
Does anyone have an idea how to debug this and resolve this? I end up cloning the parent repository again and deleting the old one :-(

:一项更新-出现这些错误时，我们正在使用两个LAN网络，它们之间具有链接.一些用户位于旧"网络中，而其他用户位于新"网络中.
每个人都迁移到新网络后，我们不再出现这些错误.

An update - while having these errors, we were working with two LAN networks that had a link between them. Some of the users where in an "old" network and others in the "new" one.
After everyone migrated to the new network, we stopped having these errors.

我希望这会有所帮助.

推荐答案

当Bitbucket服务器(我用作代码存储库的服务器)出现问题时，我收到此错误. 最终，这个问题在没有我干预的情况下消失了一段时间 (大约5-10分钟...)

I was receiving this error when there were some problems with bitbucket server (the one I am using as a code repository). And, eventually, this issue disappeared without my intervention with some time (~5-10 min or so...)

如果您使用的是 bitbucket ，则始终可以使用以下链接检查其API的状态/响应时间: http://status.bitbucket.org/

If you are using bitbucket, you can always check the status/response time of their API using the following link: http://status.bitbucket.org/

这篇关于Mercurial-解决中止的方法:汞柱内/拉入后错误:''的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！