Block a user
84 of 100 incidents are titled "Ems — TGID 9048" because /upload never resolves the talkgroup name
84 of 100 incidents are titled "Ems — TGID 9048" because /upload never resolves the talkgroup name
Fixed in 039a06d.
internal/talkgroups.py is now the single resolver — caller hint, then the call document, then the system config — and both mqtt_handler (call_start) and `run_intelligence…
LLM correlation tier decides only 3.5% of links, and the dominant fast/thin path records no fit signal
84 of 100 incidents are titled "Ems — TGID 9048" because /upload never resolves the talkgroup name
firestore.indexes.json has drifted from the live database and now duplicates two of its indexes
/dashboard does not exist, so every post-login and guard redirect lands on a 404
Wider than filed: two of the five nav destinations have no route at all either. components/Nav.tsx:19 links /watch and :25 links /network, and neither app/watch/ nor app/network/…
React error #310 white-screens /systems and /nodes
React error #310 white-screens /systems and /nodes
Closing — I filed this off stale evidence. The #310 traces I read out of the Chrome console were console history from a tab loaded at 23:23 local on 2026-08-18, two minutes before the fix…
React error #310 white-screens /systems and /nodes
Admin page redirects away before auth claims resolve, so /admin is unreachable on a cold load
/dashboard does not exist, so every post-login and guard redirect lands on a 404
Firestore rules and indexes are in source control but never deployed
Confirmed live in prod (drb.cusano.net, git_sha 861ea41, 2026-08-23 02:07 EDT) — both halves of this are still undeployed and now cause visible, misleading UI failures:
Indexes. `useIncidents…
models.py types incident location as coordinates, so PUT /incidents/{id} cannot set one
Pre-existing incidents keep an unverifiable map pin until a call links to them
Incident map pin and incident label disagree in 5 of 6 incidents