Not Displaying Graphs or Tables on Dashboard

[HungrySama17]

Running the dashboard for the first time and it looked empty, the following change needs to be made for the dashboard graphs and tables to appear on the page:

dashboard.py:

745 -    selectedModels.has(r.model) && (!cutoff || r.day >= cutoff)                                  
745 +    selectedModels.has(r.model) && (!start || r.day >= start) && (!end || r.day <= end)   

[econcepcion]

this worked for me too. thanks

[PichlAlex]

i can confirm - this works for me too.

[jakduch]

Confirming this bug — and adding a bit of root-cause detail since there are now three open PRs that all fix the same line slightly differently.

Why the dashboard renders 0 / no data

applyFilter() is called from loadData() immediately after /api/data returns. The function builds filtered datasets for the daily chart, hourly chart, model breakdown, project breakdown, sessions table and totals. Halfway through that work it hits this line:

// dashboard.py, line 745
const hourlySrc = (rawData.hourly_by_model || []).filter(r =>
  selectedModels.has(r.model) && (!cutoff || r.day >= cutoff)
);

cutoff was renamed to start/end everywhere else in applyFilter during the time-range refactor, but this one line was missed. The ReferenceError aborts the function before any of the renderers run, so:

• metric cards stay at their initial 0
• daily / hourly / model / project charts never get data passed in
• sessions table stays empty
• every UI interaction (range buttons, model toggles, rescan) re-throws because they all call applyFilter()

This also explains #76: the data is in the DB and /api/data returns it correctly (you can curl it and see all rows), it just never makes it into the rendered DOM.

The three open PRs differ in correctness

• fix: use start instead of undefined cutoff in hourly filter #73 (!start || r.day >= start) — only handles the lower bound. Loses a row if it's after end (e.g. for prev-month with explicit upper bound). Mostly works in practice because most ranges are open-ended at the top.
• fix: replace undefined cutoff with start in hourly filter #75 (!start || r.day >= start) — same as fix: use start instead of undefined cutoff in hourly filter #73.
• fix: undefined cutoff variable breaks dashboard rendering #77 — same fix.

For full correctness it should mirror the pattern used a few lines above for daily_by_model (line 660):

const hourlySrc = (rawData.hourly_by_model || []).filter(r =>
  selectedModels.has(r.model) &&
  (!start || r.day >= start) &&
  (!end || r.day <= end)
);

The difference matters for prev-month and month ranges, where end is set to the last day of the period; without the upper bound, hourly buckets bleed into the future.

Happy to open a fourth PR with the bounded version if useful, but if any of #73 / #75 / #77 are merged the dashboard will at least render — that fix on its own is what the people on this thread are asking for.

I'm running into this from a Docker setup where I needed the dashboard to actually work to validate Cowork session data; I'll be opening a few more PRs (threading on the HTTP server, query-string routing fix, ephemeral-cache pricing tier) once this one lands.

[HaydenHaines]

Fixed in PR #95. The root cause was that applyFilter used an undefined cutoff variable in the hourly data filter predicate, causing the filter to match nothing and leaving charts and tables empty. The fix replaces it with proper start/end range bounds (consistent with the other predicates in the function), plus a regression test to prevent it recurring.