Modify ↓
Opened 18 years ago
Closed 18 years ago
#554 closed defect (fixed)
Trace back while attempting to access Burndown page
Reported by: | Owned by: | Sam Bloomquist | |
---|---|---|---|
Priority: | normal | Component: | ScrumBurndownPlugin |
Severity: | normal | Keywords: | |
Cc: | Trac Release: | 0.9 |
Description
Having tried to set the plugin up, we added the custom fields but when going to the burndown page we get the traceback below. Running the burndown_job.py also seems to do nothing (the burndown table remains empty).
Oops... Trac detected an internal error: iteration over non-sequence If you think this really should work and you can reproduce it. Then you should consider to report this problem to the Trac team. Go to http://trac.edgewall.com/ and create a new ticket where you describe the problem, how to reproduce it. Don't forget to include the python traceback found below. TracGuide — The Trac User and Administration Guide Python traceback Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/trac/web/cgi_frontend.py", line 131, in run dispatch_request(req.path_info, req, env) File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 139, in dispatch_request dispatcher.dispatch(req) File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 107, in dispatch resp = chosen_handler.process_request(req) File "build/bdist.linux-x86_64/egg/burndown/burndown.py", line 113, in process_request TypeError: iteration over non-sequence
Attachments (1)
Change History (3)
comment:1 Changed 18 years ago by
Changed 18 years ago by
Attachment: | scrumburndown.1076.patch added |
---|
Note: See
TracTickets for help on using
tickets.
Sorry, I should have also mentioned this is using TRAC 0.9.3 from Ubuntu Dapper, patched using http://steffenpingel.de/patches/trac/trac-time-tracking-0.9.3.diff