Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ref(processing/store): remove references to feedback attachments option #3617

Merged
merged 3 commits into from
May 21, 2024

Conversation

aliu39
Copy link
Member

@aliu39 aliu39 commented May 16, 2024

Follow up after https://github.com/getsentry/team-replay/issues/393. We've set the option to true for all regions and tested that it works, so this is a dead code path we can remove

Relates to getsentry/sentry-javascript#11428

#skip-changelog

@aliu39 aliu39 requested a review from a team as a code owner May 16, 2024 23:04
Copy link
Member

@jjbayer jjbayer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same question as in #3604: Is this safe for self-hosted?

@aliu39
Copy link
Member Author

aliu39 commented May 20, 2024

Same question as in #3604: Is this safe for self-hosted?

Unlike 3604, this is the same for self-hosted! The change is backwards-compatible with older SDK versions, as we'll still process feedback and attachments in separate envelopes, even with the flag enabled

@aliu39 aliu39 requested review from a team and jjbayer May 20, 2024 18:19
Copy link
Member

@Dav1dde Dav1dde left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should also remove feedback.ingest-inline-attachments from Sentry now.

@aliu39 aliu39 merged commit 1551301 into master May 21, 2024
22 checks passed
@aliu39 aliu39 deleted the aliu/rm-feedback-attachments-option branch May 21, 2024 18:20
aliu39 added a commit that referenced this pull request Jun 4, 2024
…3682)

I missed this in #3617. This
condition never happens since we handle user report v2's in the
for-match loop

#skip-changelog
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants