Commit c265cc7
fix(webapp): narrow run-detail buffer fallback to RunNotInPgError
The loader's catch block was treating every RunPresenter error as a
PG miss and trying the mollifier buffer fallback. That meant a
downstream trace-query or event-repository failure after the PG row
was found would either return stale synth data (if a buffer entry
happened to still be present during the drainer materialisation race
window) or silently mask the real error.
Narrow the fallback to `RunNotInPgError` — the typed signal
RunPresenter throws specifically for "this run is not in PG and may
be in the buffer" — and re-throw all other errors. Matches the
design intent stated on the class itself.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>1 parent 6b1d36a commit c265cc7
1 file changed
Lines changed: 17 additions & 1 deletion
File tree
- apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.runs.$runParam
Lines changed: 17 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
92 | 92 | | |
93 | 93 | | |
94 | 94 | | |
95 | | - | |
| 95 | + | |
| 96 | + | |
| 97 | + | |
| 98 | + | |
| 99 | + | |
96 | 100 | | |
97 | 101 | | |
98 | 102 | | |
| |||
281 | 285 | | |
282 | 286 | | |
283 | 287 | | |
| 288 | + | |
| 289 | + | |
| 290 | + | |
| 291 | + | |
| 292 | + | |
| 293 | + | |
| 294 | + | |
| 295 | + | |
| 296 | + | |
| 297 | + | |
| 298 | + | |
| 299 | + | |
284 | 300 | | |
285 | 301 | | |
286 | 302 | | |
| |||
0 commit comments