fix(trace-item-details): allow timestamp#116321
Conversation
wmak
commented
May 27, 2026
wmak
commented
- This endpoint was defaulting to all time so queries were commonly timing out, add our usual snuba params style timestamps along with a trace style timestamp parameter with a buffer
- This endpoint was defaulting to all time so queries were commonly timing out, add our usual snuba params style timestamps along with a trace style timestamp parameter with a buffer
github-actions
Bot
added
the
Scope: Backend
![sentry-warden[bot]](https://avatars.githubusercontent.com/in/2755838?s=60&v=4){kind=small}
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 228016a. Configure here.
| if end is not None: | ||
| end = min(end, example_end) | ||
| else: | ||
| end = example_end |
There was a problem hiding this comment.
Intersection of non-overlapping ranges yields inverted timestamps
Medium Severity
When both timestamp and date range params (e.g. statsPeriod) are provided but their resulting intervals don't overlap, the intersection logic (max for start, min for end) produces start > end. This inverted range is then passed directly to FromDatetime and sent to the RPC without validation, which could cause an error or undefined query behavior downstream.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 228016a. Configure here.
2 participants
