Modify ↓
Opened 14 years ago
Last modified 8 months ago
#9137 new defect
Improper display of negative time difference
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | next-stable-1.6.x |
| Component: | timeline | Version: | 0.12dev |
| Severity: | minor | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
I accidentally had my SVN server clock set to one day in the future, so commits had a future timestamp.
My Trac sandbox runs on a different server, and is configured with SVN repository that is a readonly mirror of the one mentioned above (using svnsync).
As a result, new commits to the original SVN server are svnsync'ed to the mirror with the future timestamp, which I would expect to see in Trac source browser with negative age. What actually happens is that the age is "24 hours", which is the absolute value of the actual difference.
I set Severity to minor, since the scenario is *quite* uncommon, but thought it's worth reporting either way.. :-)
Attachments (0)
Change History (5)
comment:1 by , 14 years ago
| Milestone: | → next-minor-0.12.x |
|---|
comment:2 by , 9 years ago
| Milestone: | next-minor-0.12.x → next-stable-1.0.x |
|---|
comment:3 by , 7 years ago
| Milestone: | next-stable-1.0.x → next-stable-1.2.x |
|---|
comment:4 by , 4 years ago
| Milestone: | next-stable-1.2.x → next-stable-1.4.x |
|---|
Note:
See TracTickets
for help on using tickets.
Moved ticket assigned to next-stable-1.0.x since maintenance of 1.0.x is coming to a close. Please move the ticket back if it's critical to fix on 1.0.x.