Issue with Local Clone that is unusable.
Created originally on Bitbucket by Susan Seidlitz
I attached the bugreport from Tortoise when I try to update to my working directory. The command line give a similar error. Here is the command line output:
C:\MyRepos\CS-Apoc-Shared\src\transport>hg resolve -l ** unknown exception encountered, please report by visiting ** https://mercurial-scm.org/wiki/BugTracker ** Python 2.7.10 (default, May 23 2015, 09:44:00) [MSC v.1500 64 bit (AMD64)] ** Mercurial Distributed SCM (version 4.0.2) ** Extensions loaded: Traceback (most recent call last): File "hg", line 49, in File "mercurial\dispatch.pyo", line 60, in run File "mercurial\dispatch.pyo", line 126, in dispatch File "mercurial\dispatch.pyo", line 216, in _runcatch File "mercurial\dispatch.pyo", line 225, in callcatch File "mercurial\dispatch.pyo", line 205, in _runcatchfunc File "mercurial\dispatch.pyo", line 901, in _dispatch File "mercurial\dispatch.pyo", line 650, in runcommand File "mercurial\dispatch.pyo", line 909, in _runcommand File "mercurial\dispatch.pyo", line 898, in File "mercurial\util.pyo", line 1037, in check File "mercurial\commands.pyo", line 6212, in resolve File "mercurial\merge.pyo", line 96, in read File "mercurial\merge.pyo", line 168, in _read IndexError: list index out of range
I disabled all my extensions to simplify, but that didn’t help. I am sure that there were files that were “Unresolved” from the last time I successfully ran “hg resolve –list”, but none of the files have the “>>>>>” or “<<<<<<” sections. I would like to know exactly where Mercurial marks a file as needing resolution. That might give some clues.
Attachments: bugreport.txt