#1 closed defect (fixed)
Adding unknown revision or manifest ids breaks timeline
| Reported by: | Owned by: | Thomas Moschny | |
|---|---|---|---|
| Priority: | major | Component: | tracmtn |
| Version: | 0.0.5 | Keywords: | |
| Cc: |
Description
If, in a ticket, you include a revision id or manifest id that is not in the mtn database then the timeline then breaks. Further, it does not recover when the id does appear in the mtn database (e.g. as the result of a sync). The current work-around is to clear out the cache.
Change History (8)
comment:1 by , 17 years ago
| Status: | new → assigned |
|---|
comment:2 by , 17 years ago
comment:3 by , 17 years ago
Sorry about that. I was busy doing some other stuff, but I'll look into that problem soon (already have a patch, but it needs some testing).
comment:4 by , 17 years ago
Any news on the patch? Perhaps you can attach a diff here so I can test it?
follow-up: 7 comment:6 by , 17 years ago
- adding an unknown rev in a comment throws AutomateException
- clearing the cache does not help anymor, the exception is raised every time the ticket with the unknown rev is accessed
comment:7 by , 17 years ago
Replying to marcel@hsdev.com:
adding an unknown rev in a comment throws AutomateException
Ok. This should be fixed in 42fd0452908d9ad88ca5366a92d3b4645aefe74c.
comment:8 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Closing. Please reopen if this problem reappears.
Note:
See TracTickets
for help on using tickets.
This has been around for some time now. Is there any news on this - it's a little irritating to have to rm -rf the cache and restart the http server every couple of hours...