GLM-5.3 · Balanced
replays-self-serve-bulk-delete-system-sentry
Sentry · Python · M · 100–299 lines · 3 files
The normal review, with one generalist agent. Judge: Claude Haiku 5.5.
- Gold bugs found
- 1 of 10
- Comments published
- 3
- Comments matching a bug
- 1
- Comments not matching
- 2
- Cost of this PR
- $4.195
Published comments (3)
Table widgets render empty data when use-table-widget-visualization flag is on — With the flag on, `tableResultComponent` hardcodes empty `columns` and `tableData`, discarding `result.data`, `result.meta`, `fields`, `fieldAliases`, and the loading state. Pass the real columns and result data into `TableWidgetVisualization`, or keep the previous renderer.
fetch_error_details pairs event IDs with node data positionally, misattributing error details — Because nodestore's `get_multi` appends cache-served values last and missing nodes are filtered out, `zip(error_ids, events.values())` pairs each `ErrorEvent` with another error's title, message, or timestamp. Iterate `zip(error_ids, node_ids)` and look up `events.get(node_id)` instead.
Unvalidated `field` query params can 500 and drop error_ids from response — Unvalidated `field` params reach `generate_restricted_fieldset`, whose plain `item[field]` lookup raises `KeyError` for any name outside the replay fieldset, and a field list lacking `error_ids` makes `.get("error_ids", [])` return empty. Restrict accepted values or always pass `fields=["error_ids"]`.