DeepSeek V4.1 Flash · 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
- 0 of 10
- Comments published
- 7
- Comments matching a bug
- 0
- Comments not matching
- 7
- Cost of this PR
- $0.602
Published comments (7)
Table widget flag branch renders blank grid with empty data — Every table widget renders a blank grid once the flag is enabled, since `fields` and `result` are discarded. Feed the already-computed `result.data`, `result.meta` and `fields` into `TableWidgetVisualization`.
Error context dropped when field params are provided — Any caller passing field params gets [] for error_ids, so the new error context is silently dropped. Request the replay fields independently of the client's field list so error ids are always available.
Invalid field query param causes 500 in replay breadcrumbs — An authenticated `?field=bogus` request raises `KeyError` in `process_raw_response` and returns an unhandled 500 instead of a 400. Filter the requested fields against the known response keys before calling it.
Report tests no longer post with application/reports+json content type — Without the browser-reporting content type DRF uses the generic `JSONParser`, so these tests would still pass if `BrowserReportsJSONParser` broke. Restore `content_type="application/reports+json"` on at least one request.
Unauthenticated endpoint logs raw unvalidated report payload — This unauthenticated, CSRF-exempt endpoint lets anyone persist arbitrary content, and browser reports carry URLs, tokens and page messages into a retained warning log. Log only non-sensitive shape information instead of `raw_report`.
Replay error events mispaired by positional get_multi zip — `NodeStorage.get_multi` dedupes ids and appends cache hits after service results, so `zip` mispairs ids with another event's data and drops trailing ones. Look events up by node id instead of relying on positional order.
Mutually exclusive age/timestamp check uses truthiness, so 0 slips through — A legal value of 0 is falsy, so `timestamp`/`age` pairs like `{"timestamp": 0, "age": 5}` pass the mutually exclusive check. Use existence checks such as `"age" in self.initial_data` in `validate_timestamp` and `validate_age`.
Gold bugs found (0)
None.