bzr fails with 'iteration over non-sequence' in _get_bug_fix_properties
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
High
|
Vincent Ladeuil |
Bug Description
Starting with bzr later than version 0.15, most commands (like 'ci'), failed with a message like the one given below, while
bzr version 0.15 worked fine:
[kybic.d620-jk ~/work/frae]> bzr ci -m 'added files'
bzr: ERROR: exceptions.
Traceback (most recent call last):
File "/usr/lib/
return run_bzr(argv)
File "/usr/lib/
ret = run(*run_argv)
File "/usr/lib/
return self.run(
File "/usr/lib/
bug_property = self._get_
File "/usr/lib/
for fixed_bug in fixes:
TypeError: iteration over non-sequence
bzr 0.90.0 on python 2.4.4.final.0 (linux2)
arguments: ['/usr/bin/bzr', 'ci', '-m', 'added files']
** please send this report to <email address hidden>
-------------
Solution: I added one line before line 2206 in file builtins.py, so that 'fixes' is tested for None. This seems to have fixed the problem.
Here is the relevant section of builtins.py:
def _get_bug_
properties = []
# Configure the properties for bug fixing attributes.
if fixes is not None: # THIS LINE ADDED BY JAN KYBIC
for fixed_bug in fixes: # HERE IT USED TO FAIL
Changed in bzr: | |
assignee: | nobody → v-ladeuil |
status: | New → In Progress |
Changed in bzr: | |
status: | In Progress → Fix Committed |
Changed in bzr: | |
status: | Fix Committed → Fix Released |
Hi Jan,
Thanks for the report and the fix. I'd like to understand just when this occurs so that we can add a test for it and see if it can crop up in any other places. For me, ci does not fail when run in a newly created branch. Do you know how to reproduce this?