Edgewall Software
Modify

Opened 8 years ago

Closed 5 years ago

#10321 closed enhancement (invalid)

situations with wrong tickets timestamp

Reported by: Sergey V.Levin <slevin@…> Owned by:
Priority: normal Milestone:
Component: general Version:
Severity: normal Keywords:
Cc: Branch:
Release Notes:
API Changes:

Description

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

Attachments (2)

time_err.jpeg (14.6 KB ) - added by Sergey V.Levin <slevin@…> 8 years ago.
wrong timestamp of comment in ticket.
time2_err.jpeg (16.5 KB ) - added by Sergey V.Levin <slevin@…> 8 years ago.
Second bugshot: comment dated 42 years ago

Download all attachments as: .zip

Change History (11)

by Sergey V.Levin <slevin@…>, 8 years ago

Attachment: time_err.jpeg added

wrong timestamp of comment in ticket.

comment:1 by anonymous, 8 years ago

Perhaps did you reload the page 53 minutes before?

in reply to:  1 comment:2 by anonymous, 8 years ago

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.

comment:3 by Sergey V.Levin <slevin@…>, 8 years ago

wrong way, see next bug shot.

by Sergey V.Levin <slevin@…>, 8 years ago

Attachment: time2_err.jpeg added

Second bugshot: comment dated 42 years ago

comment:4 by anonymous, 8 years ago

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.

comment:5 by Sergey V.Levin <slevin@…>, 8 years ago

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?

comment:6 by Sergey V.Levin <slevin@…>, 8 years ago

.. 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?

comment:7 by rolechka@…, 8 years ago

We get the same error in different situations (((

comment:8 by Christian Boos, 7 years ago

Milestone: undecided

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

comment:9 by Ryan J Ollos, 5 years ago

Milestone: undecided
Resolution: invalid
Status: newclosed

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.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.
to as closed The owner will be changed from (none) to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.