[issue1184] hg recover does not fully recover database

[Alexander Chemeris]

New submission from Alexander Chemeris <ipse.reg at gmail.com>:

I killed hg process in the middle of process of commit (it was waiting for
commit message to be entered), so database was left in corrupted state. As hg
suggested, I ran 'hg recover', but it did not helped. After any command I see
this output on console:

>hg up -C ipse-local
** 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.0.1+20080525)
Traceback (most recent call last):
  File "hg", line 20, in <module>
  File "mercurial\dispatch.pyc", line 20, in run
  File "mercurial\dispatch.pyc", line 29, in dispatch
  File "mercurial\dispatch.pyc", line 45, in _runcatch
  File "mercurial\dispatch.pyc", line 364, in _dispatch
  File "mercurial\dispatch.pyc", line 417, in _runcommand
  File "mercurial\dispatch.pyc", line 373, in checkargs
  File "mercurial\dispatch.pyc", line 356, in <lambda>
  File "mercurial\commands.pyc", line 2798, in update
  File "mercurial\hg.pyc", line 287, in clean
  File "mercurial\merge.pyc", line 352, in update
  File "mercurial\localrepo.pyc", line 485, in changectx
  File "mercurial\context.pyc", line 28, in __init__
  File "mercurial\localrepo.pyc", line 452, in lookup
  File "mercurial\localrepo.pyc", line 286, in tags
  File "mercurial\localrepo.pyc", line 332, in _hgtagsnodes
  File "mercurial\context.pyc", line 116, in filenode
  File "mercurial\context.pyc", line 108, in _fileinfo
  File "mercurial\manifest.pyc", line 110, in find
  File "mercurial\revlog.pyc", line 952, in revision
mpatch.mpatchError: patch cannot be decoded

How can I get this repo working again? It would be sad to lose all my overnight
work becacuse of Mercurial. And in general it is bad that Mercurial is not as
safe to use, as svn.

PS This is under Windows XP.

----------
messages: 6319
nosy: ipse
priority: bug
status: unread
title: hg recover does not fully recover database

____________________________________________________
Mercurial issue tracker <mercurial-bugs at selenic.com>
<http://www.selenic.com/mercurial/bts/issue1184>
____________________________________________________