Modify ↓
Opened 18 years ago
Closed 18 years ago
#5919 closed defect (invalid)
Empty resolutions lead to AssertionError if logged in
| Reported by: | Owned by: | Matthew Good | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | report system | Version: | devel |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
I tried to view a ticket while being logged in but got this error instead:
2007-08-23 11:54:08,717 Trac[__init__] ERROR:
Traceback (most recent call last):
File "/home/trac/trunk/trac/web/main.py", line 381, in dispatch_request
dispatcher.dispatch(req)
File "/home/trac/trunk/trac/web/main.py", line 191, in dispatch
resp = chosen_handler.process_request(req)
File "/home/trac/trunk/trac/ticket/web_ui.py", line 144, in process_request
return self._process_ticket_request(req)
File "/home/trac/trunk/trac/ticket/web_ui.py", line 436, in _process_ticket_request
field_changes)
File "/home/trac/trunk/trac/ticket/web_ui.py", line 1035, in _insert_ticket_data
label, widget, hint = controller.render_ticket_action_control(
File "/home/trac/trunk/trac/ticket/default_workflow.py", line 239, in render_ticket_action_control
assert(resolutions)
AssertionError
The error didn't occur while beingt logged out. At the time of both tries there were no resolutions in the database. After re-adding one resolution the error went away.
Attachments (0)
Change History (2)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
No answer in 3 months. Please reopen if you can propose a valid usecase for removing all resolutions.
Note:
See TracTickets
for help on using tickets.



My initial reaction is "don't do that then". Do you have a usecase for removing all the resolutions?