Issue #66 resolved

checking for incoming from the workbench fails

Anonymous created an issue

{{{

!python

Please report this bug to http://bitbucket.org/tortoisehg/thg/issues Mercurial version (1.7.3+4-f3058dd05281). TortoiseHg version (1.9.1) Command: --nofork workbench CWD: E:\dev\working Extensions loaded: fixfrozenexts, hgsubversion, hggit, hgshelve, bookmarks, rebase, churn, mq, fetch, graphlog Python version: 2.6.6 (r266:84297, Aug 24 2010, 18:13:38) [MSC v.1500 64 bit (AMD64)] Windows version: (6, 1, 7600, 2, '') Processor architecture: x64 Traceback (most recent call last): File "tortoisehg\hgqt\repowidget.pyo", line 284, in setBundle File "tortoisehg\hgqt\thgrepo.pyo", line 39, in repository File "mercurial\bundlerepo.pyo", line 177, in init }}}

Comments (10)

  1. Steve Borho

    Line 177 of mercurial/bundlerepo is: f = open(bundlename, "rb")

    so it's trying to open the bundle and failing. Did the incoming command die? Keeping the workbench log widget open is often helpful when debugging problems like this.

  2. Anonymous

    thanks for the quick response. i tested 1.9.1507.3504 and it no longer throws an exception. on an empty incoming (with hgsubversion), the status bar will say 'Incoming aborted, ret 0'

  3. Anonymous

    "on an empty incoming (with hgsubversion), the status bar will say 'Incoming aborted, ret 0'" This should be considered a bug, although not as serious as crashing. If there are no incoming changesets, say so.

  4. Log in to comment