-
-
Notifications
You must be signed in to change notification settings - Fork 231
chore(deps): update Native SDK to v0.14.0 #5189
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
Open
github-actions
wants to merge
3
commits into
main
Choose a base branch
from
deps/modules/sentry-native
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+1
−1
Open
Changes from 2 commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Submodule sentry-native
updated
60 files
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
following up on: #5189 (comment)
thought: now I am second guessing myself
Ok ... I'm quite undecisive on this one ... here comes the bikeshedding:
If we sync these two options, shouldn't we then actually sync all options that from a "set intersection"?
Which then would be a behavioral breaking change ... wouldn't it?
My current thought is:
Do we instead only want to avoid the breaking change of changing the
sentry-nativesemantics of disable-per-default to enable-per-default in a minor release of the .NET SDK?On the other hand, we already suffered a breaking change in 0.13.5 of
sentry-nativewhere Metrics got enabled per default and we didn't change anything in thesentry-dotnetside.And another thought:
Am I overthinking this?
Are the
sentry-nativeAPIs even exposed to the .NET consumer ... so would it even matter?sentry-nativehas no "default-integration" for neither Logs nor Metrics (does it?), so if the APIs aren't called then nothing will happen, shall we then just leave the defaults ofsentry-nativeas they are.And instead in the next major release of
sentry-dotnetforward all Options that appear in both down tosentry-nativeand then keep future options and changes of the default values in sync?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's keep them consistent - so if someone does not enable logs in the .NET SDK they don't get logs (from any of the SDKs) and the same for metrics.
If that's not what we're doing now, let's change it. That's not a breaking change - it's just fixing something that's broken... It is a change in behaviour (from broken to fixed).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK ... then let's bring the sync of Logs & Metrics options back,
and follow-up with PRs to pass-through more/all options we can.