Last modified: 2008-05-09 16:41:50 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 14057 - Wrong time stamp in signature
Wrong time stamp in signature
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal minor (vote)
: ---
Assigned To: Nobody - You can work on this!
http://de.wikipedia.org/w/index.php?t...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-05-09 08:13 UTC by Ulf Hinze
Modified: 2008-05-09 16:41 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Ulf Hinze 2008-05-09 08:13:22 UTC
The diff-link shows an edit I did on wikipedia.de, which was done at 09:40, 9. Mai 2008 (see history), but the time stamp in the signature -- ~~~~ was replaced by a totally other date and time 23:55, 8. Mai 2008 (CEST).
Comment 1 Brion Vibber 2008-05-09 16:41:50 UTC
That's danged odd...

a) I did a quick check just now of server clocks -- all Apache boxes are currently consistent.

b) If the page was saved by a server with a bad clock, it should have come up with the *same* wrong time for both the save and the signature.

One remote possibility is that it was saved on a server with a bad clock (set to PST, plus a few minutes off from correct) which corrected its clock *between* the signature replacement and the page save.

However logs don't appear to show any machines being replaced in service today, which would be the most likely trigger of such a scenario.

Weeeeeeeeeird...

I'm going to consider this a freak occurrence and mark it WORKSFORME. But if you see it crop up again, do give a shout.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links