Skip to content

fix(eap-alerts): Use the correct entity key #91801

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

Merged

Conversation

shruthilayaj
Copy link
Member

Also updates all the integration tests to not mock snuba calls.
These tests should have caught that EntityKey.EAPSpans was
no longer an available option.
Also tests creating + updating + deleting a subscription in a
single tests since create uses a new RPC whereas delete
uses an older endpoint

@shruthilayaj shruthilayaj requested review from a team as code owners May 16, 2025 15:40
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label May 16, 2025
Copy link

codecov bot commented May 16, 2025

❌ Unsupported file format

Upload processing failed due to unsupported file format. Please review the parser error message:
`Error parsing JUnit XML in /home/runner/work/sentry/sentry/.artifacts/pytest.junit.xml at 1:159171

Caused by:
RuntimeError: Error validating attribute

Caused by:
    string is too long`

For more help, visit our troubleshooting guide.

@shruthilayaj shruthilayaj merged commit 85db68c into master May 16, 2025
60 checks passed
@shruthilayaj shruthilayaj deleted the shruthi/fix/use-correct-entity-key-eap-subscriptions branch May 16, 2025 16:21
andrewshie-sentry pushed a commit that referenced this pull request May 20, 2025
Also updates all the integration tests to not mock snuba calls.
These tests should have caught that EntityKey.EAPSpans was
no longer an available option.
Also tests creating + updating + deleting a subscription in a
single tests since `create` uses a new RPC whereas `delete`
uses an older endpoint
@github-actions github-actions bot locked and limited conversation to collaborators Jun 1, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants