Custom Query (7 matches)
Results (4 - 6 of 7)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10 | invalid | Timeline not implemented? | ||
| Description |
The timeline does not show any monotone commits. Is that functionality not yet implemented? |
|||
| #2 | fixed | many datetime.datetime to int compare errors as of trac rev 4475 | ||
| Description |
From casual inspection it seems that either trac switched to datetime objects or earlier checks/conversions are not present anymore in the trac trunk (rev 4475 ) Inserting conversions (for example in util/datefmt.py) helps getting rid of some, but i wonder is the mtn.dates() method should perhaps be adapted to return a list of datetime objects? |
|||
| #1 | fixed | Adding unknown revision or manifest ids breaks timeline | ||
| 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. |
|||
Note:
See TracQuery
for help on using queries.
