Modify ↓
Opened 10 years ago
Last modified 13 months ago
#11759 new defect
TypeError raises when non existent comment of ticket is modified
Reported by: | Jun Omae | Owned by: | |
---|---|---|---|
Priority: | low | Milestone: | next-stable-1.6.x |
Component: | ticket system | Version: | 0.12-stable |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
How to reproduce
- Create new ticket and add comment to the ticket
- Show "Edit" form for the comment
- Remove the comment from another browser
- Submit new comment
The issue occurs with both 0.12-stable and 1.0-stable.
2014-09-16 12:15:40,582 Trac[main] ERROR: Internal Server Error: Traceback (most recent call last): File "/src/tracdev/git/trac/web/main.py", line 529, in _dispatch_request dispatcher.dispatch(req) File "/src/tracdev/git/trac/web/main.py", line 243, in dispatch resp = chosen_handler.process_request(req) File "/src/tracdev/git/trac/ticket/web_ui.py", line 174, in process_request return self._process_ticket_request(req) File "/src/tracdev/git/trac/ticket/web_ui.py", line 499, in _process_ticket_request ticket.modify_comment(change['date'], req.authname, comment) TypeError: unsubscriptable object
Attachments (0)
Change History (5)
comment:1 by , 10 years ago
Milestone: | 0.12.7 → 1.0.3 |
---|---|
Priority: | normal → low |
comment:2 by , 10 years ago
Milestone: | 1.0.3 → next-stable-1.0.x |
---|
Retargeting tickets in milestone:1.0.3 that have no owner. Please retarget as appropriate.
comment:3 by , 8 years ago
Milestone: | next-stable-1.0.x → next-stable-1.2.x |
---|
Moved ticket assigned to next-stable-1.0.x since maintenance of 1.0.x is coming to a close. Please move the ticket back if it's critical to fix on 1.0.x.
comment:4 by , 4 years ago
Milestone: | next-stable-1.2.x → next-stable-1.4.x |
---|
Note:
See TracTickets
for help on using tickets.
Maybe too "corner-case" of a problem to be worth fixing on 0.12-stable. I'd suggest moving it on 1.0.3.