Custom Query (7 matches)
Results (1 - 3 of 7)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#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. |
|||
#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? |
|||
#7 | fixed | Trac ticket #4972 needs a change in the mtn plugin | ||
Description |
I've just done this in backend.py @@ -382,6 +382,12 @@ class MonotoneRepository(Repository): """ return dates(self.mtn.certs(rev).get('date', [])) + def close(self): + """ + Do whatever is needed to close a repository. + Nothing yet, we just dont raise the exception like our parent does. + """ + Other than that, i'm clueless what would need to be done in that method. |