fix(Replay): Use Sentry Prefix for Project_id#104296
Merged
cliffordxing merged 1 commit intomasterfrom Dec 3, 2025
Merged
Conversation
github-actions
bot
added
the
Scope: Backend
srest2021
approved these changes
Dec 2, 2025
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.
2 participants
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.
As title says, this PR uses sentry prefix to query for project_id (
sentry.project_id), as it was causing the following issue:The reason this is causing an issue is because
project_iditself is not queryable as an attribute, since it is a top level protobuf field, which causes the following line to be null on the frontend:Thus, we change our query to use the sentry prefix to receive the proper data. The reason this was not caught in a unit test previously is because we were manually adding the project_id in the attributes dummy data, allowing it to be queried. To test this new change, we remove the attribute and see that it still works as expected.