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

Disable performance when client feature disabled #415

Closed
wants to merge 1 commit into from

Conversation

Jake-Shadle
Copy link
Contributor

The new performance features rely on the client feature being enabled, and when it's not enabled sentry-core fails to compile, this just gates the entire performance module behind the client feature for now so that it at least compiles, as it seemed non-trivial to untangle types like TransactionOrSpan from client.

@Swatinem
Copy link
Member

Oh well, that was a major oversight. This also means our test matrix is incomplete, as this should have been caught ideally.

And I think we have to jump through the hoops and make sure the API at least exists and compiles even without the client, in case someone really wants to instrument their libraries with sentries perf API (though unlikely).

@Swatinem
Copy link
Member

I opened #416 instead which also correctly tests the feature flag in CI, and keeps the API around if the feature is not specified.

@Swatinem Swatinem closed this Jan 24, 2022
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.

2 participants