This repository was archived by the owner on Oct 23, 2026. It is now read-only.
Repository navigation
fix(replay): support user.display field in explore - #1639
Closed
sentry[bot] wants to merge 1 commit into
Closed
sentry[bot] wants to merge 1 commit into
sentry[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Contributor
|
Closing as part of archiving getsentry/cli; the CLI now lives in getsentry/toolkit. Ported as getsentry/toolkit#1605. |
BYK
added a commit
to getsentry/toolkit
that referenced
this pull request
Oct 23, 2026
`sentry explore --dataset replays --field user.display` failed with a `ValidationError` because the replay field map had no `user.display` entry ([CLI-1EZ](https://sentry.sentry.io/issues/7439000688/)). Agents reach for it because the Discover datasets support it. It now resolves to the same user label the replay list already shows (display name, then username, email, id, IP) and requests the `user` root field from the API. Ported from getsentry/cli#1639, which is being closed with the repo archive. <!-- junior-request-attribution:start --> via **BYK**. <!-- junior-request-attribution:end --> <!-- junior-session-footer:start --> <!-- junior-conversation-id:local%3Aweb%3Ad9c5b0de1ecf3c7114be7025 --> -- [View Junior Session in Sentry](https://sentry.sentry.io/explore/conversations/local%3Aweb%3Ad9c5b0de1ecf3c7114be7025/?project=4510944073809921) <!-- junior-session-footer:end --> Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com> Co-authored-by: BYK <[email protected]>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes a
ValidationErrorwhen users (including AI agents like Codex/Cursor) attempt to use--field user.displaywithsentry explore --dataset replays.The root cause was that
user.displaywas missing from theREPLAY_FIELD_RESOLVERSmap and thereplayRequestRootswitch statement inpackages/cli/src/lib/replay-search.ts. As a result,isSupportedReplayField('user.display')returnedfalse, causing the CLI to reject the field as unsupported.The fix involves two small additions to
packages/cli/src/lib/replay-search.ts:"user.display": (replay) => getReplayUserLabel(replay)toREPLAY_FIELD_RESOLVERS.case "user.display":to thereplayRequestRootswitch, ensuring it returns"user"as the top-level API field.New unit tests have been added to
test/lib/replay-search.test.tsto cover these changes.Fixes CLI-1EZ
@sentry <feedback>: Autofix iterates on these changes@sentry stop iterating: Autofix stops iterating on this runThis PR was automatically generated by Sentry. You can adjust this setting at any time.