Note this doesn't affect overall counts, the tables, etc. This is strictly just the daily chart visualization.
Basically, CF Analytics Engine will adjust the result set based on whether DST is in effect – below the America/Toronto timezone returns 05:00 for "midnight" until 03-11, after which DST kicks in, and midnight is now 04:00 in UTC.
This result set is fine, but since it's merged with a JavaScript-calculated result set (where the math does not account for DST) to produce buckets where there is no data (CF will not return a row if count is 0), you get this mangled object with some DST-aware data points and some not.
Note this doesn't affect overall counts, the tables, etc. This is strictly just the daily chart visualization.
Basically, CF Analytics Engine will adjust the result set based on whether DST is in effect – below the
America/Toronto
timezone returns05:00
for "midnight" until03-11
, after which DST kicks in, and midnight is now04:00
in UTC.This result set is fine, but since it's merged with a JavaScript-calculated result set (where the math does not account for DST) to produce buckets where there is no data (CF will not return a row if
count
is 0), you get this mangled object with some DST-aware data points and some not.