Issue #49 resolved

pull results in KeyError

Dennis Schridde
created an issue

When I try to pull one of my local checkouts, hg will raise a KeyError somewhere in dulwich. See attached logfile.

Comments (8)

  1. xumix

    Same bug for me c:\Projects\Metro>hg -v pull pulling from git+https://github.com/olton/Metro-UI-CSS.git ** Unknown exception encountered with possibly-broken third-party extension hggit ** which supports versions 2.3.1 of Mercurial. ** Please disable hggit and try your action again. ** If that fixes the bug please report it to https://bitbucket.org/durin42/hg-git/issues ** Python 2.7.3 (default, Apr 10 2012, 23:24:47) [MSC v.1500 64 bit (AMD64)] ** Mercurial Distributed SCM (version 2.3.2) ** Extensions loaded: color, children, graphlog, convert, extdiff, highlight, progress, eol, keyword, mq, rebase, fetch, hggit, purge Traceback (most recent call last): File "hg", line 42, in <module> File "mercurial\dispatch.pyo", line 28, in run File "mercurial\dispatch.pyo", line 65, in dispatch 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\extensions.pyo", line 189, in wrap File "hgext\color.pyo", line 364, in colorcmd 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\extensions.pyo", line 144, in wrap File "mercurial\util.pyo", line 471, in check File "hgext\mq.pyo", line 3528, in mqcommand File "mercurial\util.pyo", line 471, in check File "mercurial\extensions.pyo", line 144, in wrap File "mercurial\util.pyo", line 471, in check File "hgext\rebase.pyo", line 700, in pullrebase File "mercurial\util.pyo", line 471, in check File "mercurial\commands.pyo", line 4614, in pull File "C:\Projects\hg-git\hggit\hgrepo.py", line 14, in pull return git.fetch(remote.path, heads) File "C:\Projects\hg-git\hggit\git_handler.py", line 191, in fetch refs = self.fetch_pack(remote, heads) File "C:\Projects\hg-git\hggit\git_handler.py", line 990, in fetch_pack commit() File "dulwich\object_store.pyo", line 575, in commit File "dulwich\object_store.pyo", line 549, in move_in_pack File "dulwich\pack.pyo", line 1103, in sorted_entries File "dulwich\pack.pyo", line 1091, in iterentries File "dulwich\pack.pyo", line 1238, in _walk_all_chains File "dulwich\pack.pyo", line 1248, in _walk_ref_chains File "dulwich\pack.pyo", line 1244, in _ensure_no_pending KeyError: ['af91eebc3c620505b1beeb0e00fa535ce561fe42', '1997f6421c7432c24b754752f2378c0e5c325d1e', '7b6e2fffa6338049ce54ec7daaa4c24017f2a14b', 'e825eba89e11474b3e5c262dbe64716ba7928a4e', '157a989d5389103fb201e138ced04b49596eac75', '039a35c5378d138335545a63bcada4c0ab35ebf0', 'b41980a9996c02e82fb1a680c28689c1be09148e', '592f37683b09e9fe5f48de1d0e11edf60ea07669', 'bde4758852e13e99956dd6238a19abd7f48f9ca7', 'a5feca9e598406381a3b02e3cf083e2c5b8abb4b', 'b11028cf4e0b05d59eac949dff237b148915e9fd', 'fcc4d2eafbc135c69c3a83c3bc78118c9261dfdb', '0d9a0eb5bbd70d96fac9475633ccc30dc1f9d969', '301fe09b59c6354d7dad8c173f0c6ae0480d2192', 'b1aaae066c1d7b8d70451fd2c8c2ba8697028532', '7a8e96a1304bd945e99759cf82d01243d888862a', 'a3dbb9c46ac6fff834da06dc17b44ea10a2893b6', '85b0e490c5a9e97633598540a2830da09b3eaa22', '98ec06be860887f1c6ccf842201087429095a825', 'f1dbcfef309ca027b8edb5125a1e2cd08e56cce8', 'fac0cb1a4f90062b495b3f1ca1967f661ef4b172', 'f88be9e70b5e4fa194609e8bdb646a930a09d41c', 'af6e22d336c7ee6f43c2a619b3e67b7dcaa58be6', 'ee2c49b88c7237e7c9d5e82dc3d010347795d17e', 'f5e56f8750e232e3aa3ee2dc66d91759f44e71df']

  2. xumix

    Same problem here TortoiseHG version 2.5.1 with Mercurial-2.3.2, Python-2.7.3, PyQt-4.9.1, Qt-4.8.0 Ah, sorry for duplicating my comment And it is actually dulwich bug

  3. Zoltán Lehóczky

    I'd add that the error seems to start appearing when branches are pushed to the git repo. I can also confirm that l33t's fix works (why aren't you submitting a pull request BTW?).

  4. Log in to comment