Problem
On the Usage page, selecting Past 24h and switching the Breakdown to Hour renders a table that only lists hours with activity, ordered newest first.
With sparse activity the list jumps around and reads as broken. For example the screenshot showed:
4 PM $0.22
3 PM $5.44
2 PM $6.07
1 PM $0.30
6 PM $1.36
5 PM $1.31
The 18 zero-activity hours between 1 PM and 6 PM are silently missing, so it looks like the hours are out of order.
What I verified
- The underlying ordering is correct (chronological by UTC bucket instant, displayed newest-first), and the hour labels do use the system timezone (
window.timeZone from makeWindow, confirmed against the local transcript data — America/Sao_Paulo here).
- The real defect is presentation: the hourly breakdown drops zero-activity buckets, unlike the chart above it, which always renders every period in the 24h window.
Proposed fix
Make the hourly breakdown render every hour in the window (zero-filled) in chronological order, matching the chart. The 24h window is small enough that a complete list is readable, and it removes the misleading gaps. Daily windows (up to 90 periods) keep the existing newest-first behavior.
Problem
On the Usage page, selecting Past 24h and switching the Breakdown to Hour renders a table that only lists hours with activity, ordered newest first.
With sparse activity the list jumps around and reads as broken. For example the screenshot showed:
The 18 zero-activity hours between
1 PMand6 PMare silently missing, so it looks like the hours are out of order.What I verified
window.timeZonefrommakeWindow, confirmed against the local transcript data —America/Sao_Paulohere).Proposed fix
Make the hourly breakdown render every hour in the window (zero-filled) in chronological order, matching the chart. The 24h window is small enough that a complete list is readable, and it removes the misleading gaps. Daily windows (up to 90 periods) keep the existing newest-first behavior.