Claude Sonnet 5.5 · Heavy
replays-self-serve-bulk-delete-system-sentry
Sentry · Python · M · 100–299 lines · 3 files
The generalist plus 9 specialist lens agents in parallel, then the same verify and dedup steps. Judge: Claude Haiku 5.5.
- Gold bugs found
- 3 of 10
- Comments published
- 4
- Comments matching a bug
- 3
- Comments not matching
- 1
- Cost of this PR
- $6.899
Published comments (4)
Error timestamps (seconds) compared against rrweb timestamps (milliseconds) — If the units differ, error entries sort before every breadcrumb and the AI summary gets the wrong chronology. Normalize both sides in `gen_request_data`, for example by multiplying the `error_events` timestamp by 1000 before comparing it to the rrweb `timestamp`.
Age/timestamp exclusivity check ignores a value of 0 — A valid value of 0 is falsy, so a report with both fields passes when one of them is 0. In `validate_timestamp` and `validate_age`, check `is not None` on `self.initial_data.get(...)` instead of truthiness.
Test with max_segment_id=None never exercises the null guard — Because `delete_matched_rows` is patched, the `max_segment_id` None row never reaches `_make_recording_filenames`, so the test passes even without the guard. Add a test that runs `_make_recording_filenames` or an unmocked `delete_matched_rows` with None and asserts no filenames are produced.
Error details paired with wrong event IDs via zip over dict values — `nodestore.backend.get_multi` doesn't guarantee that the order of `events.values()` matches `error_ids`, and missing nodes may be omitted. This can attach the wrong title, message and timestamp to an event ID.