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.
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
[API] Add synchronous gauge #3029
[API] Add synchronous gauge #3029
Changes from 2 commits
63fa75e
095435a
bd8cb23
eecf89f
60df532
855f86d
f84a896
c9e40a5
55afe83
56bdf77
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
not blocking the merge. Seems
T
should be integer or float types? If so, could it be asserted explicitly like below?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.
Is inserting a new
InstrumentType
ofkGauge
a SDK breaking change and also break the ABI? Should it be included only forOPENTELEMETRY_ABI_VERSION_NO >= 2
?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.
It won't be ABI breaking for API, as
InstrumentType
is not part of API surface. And we don't guarantee SDK ABI compatibility. It could be breaking change for custom exporters which use theswitch
on thisenum
without handlingdefault
case, but this can be added in the changelog.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.
This has been discussed before:
#3029 (comment)
The code as written is fine:
I don't think we should document that in the changelog for the SDK, by definition every SDK change can (and most of the time does) break the SDK ABI.
@ThomsonTan Please remove the change requested then, as this blocks the merge.