Modify ↓
Opened 10 years ago
Closed 9 years ago
#12428 closed enhancement (duplicate)
Log stacktrace from exceptions when generating navigation items
| Reported by: | Ryan J Ollos | Owned by: | Christian Boos |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | web frontend | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Suggested in comment:13:ticket:12385, the stacktrace should be logged when an exception occurs generating navigation items: tags/trac-1.0.10/trac/web/chrome.py@:811-816#L809.
Also, we should consider logging the stacktrace when rendering the template (comment:16:ticket:12385): tags/trac-1.0.10/trac/web/chrome.py@:1130-1133#L1108. The stacktrace is printed when use_chunked_encoding: tags/trac-1.0.10/trac/web/chrome.py@:1188-1190#L1165. However, there may be a reason this was not done (comment:18:ticket:12385).
Attachments (0)
Change History (3)
comment:1 by , 9 years ago
| Milestone: | next-stable-1.0.x → next-stable-1.2.x |
|---|
comment:2 by , 9 years ago
| Milestone: | next-stable-1.2.x → next-dev-1.3.x |
|---|---|
| Owner: | set to |
| Status: | new → assigned |
Depends on #12680.
comment:3 by , 9 years ago
| Milestone: | next-dev-1.3.x |
|---|---|
| Resolution: | → duplicate |
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
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.