Modify ↓
Opened 17 years ago
Closed 15 years ago
#7926 closed defect (worksforme)
enhanced error during upgrade
| Reported by: | Owned by: | Remy Blank | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | 0.11.2.1 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
I wanted to know what plugin is failing during an upgrade, so I modified Environment.upgrade to give me that information via an exception. patch to follow.
Attachments (1)
Change History (4)
by , 17 years ago
| Attachment: | trac-upgrade-exception.patch added |
|---|
comment:1 by , 17 years ago
| Milestone: | → 0.12 |
|---|
comment:2 by , 16 years ago
| Milestone: | 0.12 → next-minor-0.12.x |
|---|---|
| Owner: | set to |
I'll implement comment:1, but probably not for 0.12.
comment:3 by , 15 years ago
| Milestone: | next-minor-0.12.x |
|---|---|
| Resolution: | → worksforme |
| Status: | new → closed |
Trunk now logs the current upgrade participant, and performs each upgrade in a separate transaction, so this is no longer an issue.
Note:
See TracTickets
for help on using tickets.



Well, doing a commit after each partial upgrade seems wrong.
You should rather take note of the currently executing upgrade, then show the culprit when catching the exception, i.e. something like:
(untested)