Skip to content

Conversation

@ceorourke
Copy link
Member

Filter out None values during combined rule serialization - these are hitting exceptions during the individual serialization and returning None in the base serializer, mainly due to RPC failures looking up related integrations. It's better to at least return what we can rather than error completely.

Fixes SENTRY-5E0V

@ceorourke ceorourke requested a review from a team as a code owner December 1, 2025 21:35
@ceorourke ceorourke requested a review from cathteng December 1, 2025 21:35
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Dec 1, 2025
@ceorourke ceorourke merged commit f7dc6e8 into master Dec 1, 2025
68 checks passed
@ceorourke ceorourke deleted the ceorourke/serialize-none-exception branch December 1, 2025 22:15
jerryzhou196 pushed a commit that referenced this pull request Dec 1, 2025
Filter out `None` values during combined rule serialization - these are
hitting exceptions during the individual serialization and returning
`None` in the [base
serializer](https://github.com/getsentry/sentry/blob/master/src/sentry/api/serializers/base.py#L120-L122),
mainly due to RPC failures looking up related integrations. It's better
to at least return what we can rather than error completely.

Fixes SENTRY-5E0V
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants