Issue #1175 resolved
created an issue

Hi TortoiseHg has started giving me the error below (everytime, i.e. I cannot open TortoiseHg).

This is for any Repo and is happening on two PCs (WinXP SP3 x86 and Win7 Ultimate SP1 x64).



Mercurial version (1.9.2). TortoiseHg version (2.1.3) Command: --nofork workbench CWD: C:\Users\Andy\Desktop\Community Cart Encoding: cp1252 Extensions loaded: Python version: 2.6.6 (r266:84297, Aug 24 2010, 18:13:38) [MSC v.1500 64 bit (AMD64)] Windows version: (6, 1, 7601, 2, 'Service Pack 1') Processor architecture: x64 ** Qt-4.7.1 PyQt-4.8.3 Traceback (most recent call last): File "tortoisehg\hgqt\run.pyo", line 547, in call File "tortoisehg\hgqt\workbench.pyo", line 906, in run File "tortoisehg\hgqt\workbench.pyo", line 69, in init File "tortoisehg\hgqt\workbench.pyo", line 836, in restoreSettings File "tortoisehg\hgqt\reporegistry.pyo", line 343, in reloadModel File "tortoisehg\hgqt\repotreemodel.pyo", line 99, in init File "tortoisehg\hgqt\repotreemodel.pyo", line 318, in loadSubrepos File "tortoisehg\hgqt\repotreeitem.pyo", line 267, in appendSubrepos File "mercurial\util.pyo", line 169, in get File "mercurial\context.pyo", line 79, in substate File "mercurial\subrepo.pyo", line 37, in state File "mercurial\context.pyo", line 82, in contains File "mercurial\util.pyo", line 169, in get File "mercurial\context.pyo", line 64, in _manifest File "mercurial\manifest.pyo", line 54, in read File "mercurial\revlog.pyo", line 867, in revision File "mercurial\revlog.pyo", line 305, in rev LookupError: 00manifest.i@035349a3598e: no node


help :os

Comments (6)

  1. atwright147 reporter

    Please ignore, this was due to an earlier problem with a corrupt repository.

    I hadn't realised that TortoiseHg looks through all repos that are in the "registry" when it opens.


  2. Steve Borho

    repotreeitem: Handle all exceptions that may happen during appendSubrepos (closes #1175)

    We want to handle all exception that may happen while the reporegistry is loading the subrepos, because otherwise THG may not load at all.

    Some expected exceptions are silently handled, marking the corresopnding repo and/or subrepos as invalid. For all other exceptions we show a warning message to the user, and we let him continue or abort, in which case the exception is re-raised, so that we get the full exception error dialog.

    Note that #1175 is marked as a duplicate of #995 on bitbucket, but these two issues are totally unrelated.


  3. Log in to comment