situations with wrong tickets timestamp

[Sergey V.Levin <slevin@…>]

Bug shot in attchment. I can't replay this error. But in 20+ trac and that effect founded in each trac.

[Sergey V.Levin <slevin@…>]

wrong timestamp of comment in ticket.

[anonymous]

Perhaps did you reload the page 53 minutes before?

[anonymous]

Replying to anonymous:

Perhaps did you reload the page 53 minutes before?

No, I think he reloaded the page (28+60+26)-53=114-53=61 minutes before, then it remained unreloaded until 18:26.

[Sergey V.Levin <slevin@…>]

wrong way, see next bug shot.

[Sergey V.Levin <slevin@…>]

Second bugshot: comment dated 42 years ago

[anonymous]

1970-01-01 means you created the ticket when your underlying operating system had an unconfigured datetime.

Everything can be explained without suspecting a bug in trac.

[Sergey V.Levin <slevin@…>]

so, about last bugshot, that ticket was created with correct timestamp, on bugshot we're can see a first comment on normal ticket (was created 8 weeks ago). About system time on host. That was be correct all time after start system in production. Waht is it mean "unconfigured datetime" ? Ok - possible it's not a trac error, then where is error in that case?

[Sergey V.Levin <slevin@…>]

.. may be the solution was get the timestamp from the system twice and check the different, and if different more then some value - try to get time again.. no?

[rolechka@…]

We get the same error in different situations (((

[Christian Boos]

All the tickets for {20} from last year have probably been seen multiple times by now, yet are still to be triaged…

[Ryan J Ollos]

I don't know what to make of this, so closing the ticket. Please raise the issue on the MailingList if you are still experiencing it.