fix(web): keep synthetic fingerprints out of the errors sparkline query

[JeremyFunk]

What broke

Loading /errors returned a 500 from errorsSpark:

Cannot parse string 'alert:550bb2c5-…:scraper' as UInt64: syntax error at begin of string

error_issues.fingerprint_hash is shared across three issue kinds:

kind	fingerprint
error	decimal UInt64 string from ClickHouse
alert	alert:{ruleId}:{groupKey}
integration	planetscale:{database}:{event}

The errors hub sent every visible issue's fingerprint to the batched sparkline
query, which lowers the list into FingerprintHash IN (toUInt64('…'), …). A
single alert-backed issue on screen made ClickHouse reject the whole batch — so
the sparklines failed for every row in the list, not just that one.

Issue detail never hit this because ErrorIssueReadModelsService.getIssue
already skips the warehouse for non-error kinds.

Fix

Apply the same guard before the round-trip, as sparkFingerprintHashes() in
lib/models/error-signal.ts. Alert and integration rows already degrade
correctly: buildErrorSignals falls back to an empty series, and
getErrorsSpark short-circuits an empty list, so a view holding only alert
issues skips the request altogether.

Not covered here

/internal/query-engine/errors-spark still lowers a caller-supplied list
straight into toUInt64(), so a future caller passing a synthetic key gets a
500 rather than a 400. Tightening the shared FingerprintHash primitive to
decimal-only would be wrong — parseFingerprintHashes in the v2 issues route
legitimately filters Postgres by alert: values — so that hardening would need
to live at the warehouse-bound boundary specifically. Left out of this fix.

Verification

• bun run --cwd apps/web test src/lib/models/error-signal.test.ts — 12 passed,
  including a new case built from the fingerprint in the failing trace
• bun run --cwd apps/web typecheck — clean

Not verified in a browser: reproducing needs an alert-backed issue in the hub
list, which local data does not have. The failing path is a data-selection
choice, covered by the unit test instead.

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[github-actions]

🍁 Maple PR preview

Warning

Preview cleanup could not be confirmed. The Alchemy teardown outcome was skipped.

Final commit bb31699 · View workflow run