#7 py stacktrace when commit failes

open
nobody
None
5
2012-09-14
2009-04-02
kiilerix
No

[mk@localhost hacking]$ qct
Auto-detected Mercurial repository
Error code 255 not expected
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/qctlib/gui_logic.py", line 801, in commitSelected
self.vcs.commitFiles(checkedItemList, msg)
File "/usr/lib/python2.6/site-packages/qctlib/vcs/hg.py", line 538, in commitFiles
self.hgcmd(['commit', '-l', filename] + commitFileNames)
File "/usr/lib/python2.6/site-packages/qctlib/vcs/hg.py", line 129, in hgcmd
(out, err) = runProgramStderr([self.hg_exe] + args, expectedexits=okresults)
File "/usr/lib/python2.6/site-packages/qctlib/utils.py", line 191, in runProgramStderr
raise ProgramError(progStr, out)
qctlib.utils.ProgramError: /usr/bin/hg commit -l /tmp/tmpWdVTDA foo.py:
^Z
[1]+ Stopped qct
[mk@localhost rdp-hacking]$ /usr/bin/hg commit -l /tmp/tmpWdVTDA foo.py
abort: unresolved merge conflicts (see hg resolve)
[mk@localhost rdp-hacking]$

It would be nice if that situation was handled nicer somehow. If the commit doesn't succeed then the output from hg should be shown to the user.

Using qct-1.7-2.fc11.i586

Discussion

  • Steve Borho

    Steve Borho - 2009-04-03

    Qct is basically unmaintained these days. All of my efforts are directed at TortoiseHg. The TortoiseHg commit tool does handle this issue much better than Qct.

    I'll accept patches for bugs, but I have no time to fix them myself.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks