Project

General

Profile

Bug #9537

One month offset in displayed data between time changes

Added by Michael Virgilio about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
Category:
Status Traffic Totals
Target version:
-
Start date:
05/19/2019
Due date:
% Done:

0%

Estimated time:
Affected Version:
Affected Architecture:

Description

There is a bug in the Status > Traffic Totals package with a one-month offset in displaying data. The offset occurs and resolves in the months where there is a transition between summer time and regular time.

For example, in the US, summer time ends in November. The extra hour in the month causes November to appear twice in the table and graph. Summer time starts in March, so there is the loss of an hour, causing March to not appear in the data table and graph. Technically, December is showing as the second November entry, January is showing as December, etc., but the one hour offset causes the data to be displayed incorrectly.

My guess is that the inconsistency is due to a difference in time zone handling between the tool(s) doing the logging and the web interface. One is likely using GMT (which doesn't reflect a difference between summer time and regular time) and the other is likely using the local time zone.

Also available in: Atom PDF