Modify ↓
Ticket #9038 (closed defect: fixed)
Opened 2 years ago
Last modified 2 years ago
Latest multirepos revision chokes on revision log links
| Reported by: | Robert Rossmair <r.rossmair@…> | Owned by: | rblank |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.12 |
| Component: | wiki system | Version: | 0.12dev |
| Severity: | major | Keywords: | multirepos "revision log links" |
| Cc: | |||
| Release Notes: | |||
| API Changes: | |||
Description
If no default repository is defined, a revision log link like
r1:3
causes Trac 0.12multirepos-r9124 to throw an internal error
AttributeError: 'NoneType' object has no attribute 'reponame'
I understand that such a link can't be resolved in a multi-repository environment, but it shouldn't throw an internal error at least.
The TracLinks Wiki page for example can't be displayed (nor edited) any more, because it contains such links.
It would be nice by the way to document the link syntax (changesets, revision logs etc.) for multirepos-Trac, so that we don't need to resort to trial and error. Or have I overlooked existing documentation?
Attachments
Change History
comment:1 Changed 2 years ago by rblank
- Owner set to rblank
comment:2 Changed 2 years ago by rblank
- Resolution set to fixed
- Status changed from new to closed
Fixed in [9165].
Note: See
TracTickets for help on using
tickets.
Agreed, we shouldn't throw an internal error. I'll fix that.
About the documentation, it's a work in progress. It's the same syntax as for scoped links, for example to show revision 123 on repository repos, you use [123/repos].