"unknown exception encountered, details follow"
Matt Mackall
mpm at selenic.com
Sat Apr 25 20:39:44 CDT 2009
On Sat, 2009-04-25 at 13:46 -0700, Scott David Daniels wrote:
> Matt Mackall wrote:
> > On Sat, 2009-04-25 at 11:38 -0700, Scott David Daniels wrote:
> >
> >> Matt Mackall wrote:
> >>
> >>> On Sat, 2009-04-25 at 10:03 -0700, Scott David Daniels wrote:
> >>>
> >>>
> >>>> In updating Cython, I just got the exception below. As I am not
> >>>> currently fiddling Cython, I can leave all data here if you want to be
> >>>> able to replicate. I tried to show the state that I'm in. Let me know
> >>>> if someone wants to try to replicate (or if not); I'm willing to spend
> >>>> some time on it with someone who knows the code. If I hear from
> >>>> nobody, this offer expires in a week.
> >>>>
> >>>> --Scott David Daniels
> >>>> Scott.Daniels at Acm.Org
> >>>>
> >>>>
> >>>> C:\Projects\cython>hg pull -u
> >>>> pulling from http://hg.cython.org/cython/
> >>>> searching for changes
> >>>> adding changesets
> >>>> adding manifests
> >>>> adding file changes
> >>>> transaction abort!
> >>>> rollback completed
> >>>> ** unknown exception encountered, details follow
> >>>> ** report bug details to http://www.selenic.com/mercurial/bts
> >>>> ** or mercurial at selenic.com
> >>>> ** Mercurial Distributed SCM (version 1.2.1)
> >>>> ** Extensions loaded: win32text
> >>>> Traceback (most recent call last):
> >>>> File "hg", line 27, in <module>
> >>>> File "mercurial\dispatch.pyc", line 16, in run
> >>>> File "mercurial\dispatch.pyc", line 25, in dispatch
> >>>> File "mercurial\dispatch.pyc", line 41, in _runcatch
> >>>> File "mercurial\dispatch.pyc", line 372, in _dispatch
> >>>> File "mercurial\dispatch.pyc", line 247, in runcommand
> >>>> File "mercurial\dispatch.pyc", line 417, in _runcommand
> >>>> File "mercurial\dispatch.pyc", line 377, in checkargs
> >>>> File "mercurial\dispatch.pyc", line 371, in <lambda>
> >>>> File "mercurial\util.pyc", line 718, in check
> >>>> File "mercurial\commands.pyc", line 2174, in pull
> >>>> File "mercurial\localrepo.pyc", line 1495, in pull
> >>>> File "mercurial\localrepo.pyc", line 2043, in addchangegroup
> >>>> File "mercurial\revlog.pyc", line 1221, in addgroup
> >>>> mpatch.mpatchError: patch cannot be decoded
> >>>>
> >>>>
> >>> Please send us the output of hg verify.
> >>>
> >>>
> >> C:\Projects\cython>hg verify
> >> checking changesets
> >> checking manifests
> >> crosschecking files in changesets and manifests
> >> checking files
> >> 905 files, 1840 changesets, 4336 total revisions
> >>
> >
> > Looks like I didn't notice this was a pull the first time around. So
> > either there's a verify problem on the server or something is going
> > wrong over the wire. Is this error repeatable? If not, the server may be
> > sporadically hanging up on you. Might be related to this:
> >
> > http://hg.cython.org/
> >
> > The server is temporarily unable to service your request due to
> > maintenance downtime or capacity problems. Please try again later.
> >
> It's back up, and I get the same response. Should I instrument it somehow?
Seems there's some repository damage on the server side. Works fine up
to here:
hg clone -r 1944 -U --debug http://hg.cython.org/cython cython2
But revlogs that are part of later revisions have gone missing:
http://hg.cython.org/cython/rev/1945
http://hg.cython.org/cython?bases=7975aadd82b76897c07336036305ed49b08549e8&cmd=changegroupsubset&heads=7975aadd82b76897c07336036305ed49b08549e8
Probably need to bring the folks on the server side into the loop here.
--
http://selenic.com : development and support for Mercurial and Linux
More information about the Mercurial
mailing list