-
Notifications
You must be signed in to change notification settings - Fork 821
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
fix!: change status codes from grpc status codes #1644
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1644 +/- ##
==========================================
+ Coverage 91.31% 91.35% +0.03%
==========================================
Files 165 165
Lines 5066 5042 -24
Branches 1044 1040 -4
==========================================
- Hits 4626 4606 -20
+ Misses 440 436 -4
|
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.
Thanks for doing this. I know it was a huge amount of work
@@ -51,7 +51,7 @@ export class Span implements api.Span, ReadableSpan { | |||
readonly instrumentationLibrary: InstrumentationLibrary; | |||
name: string; | |||
status: api.Status = { | |||
code: api.CanonicalCode.OK, | |||
code: api.StatusCode.UNSET, |
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.
Why do we have "UNSET" now as default ?
Is this required by spec if so where is it?
Currently all spans are being exported with status "UNSET" previously if they were ok they were exported as "OK"
@dyladan ^^
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 I have found this to be set as default, but shouldn't the span be set to "OK" once it is finished and there were no errors ?
Co-authored-by: Daniel Dyla <[email protected]>
Co-authored-by: Daniel Dyla <[email protected]>
…y#1644) The type `V4Connection` re-introduced in open-telemetry#1170 is missing any type definitions or imports for `Document`, breaking the build with Typescript strict mode. `V4Connection` in `types.ts` is not referenced anywhere (the type definition in `internal-types.ts` is used. So lets just drop this type definition. BREAKING CHANGE: removes the broken exported type `V4Connection`. Fixes open-telemetry#1639 Signed-off-by: Simon Berz <[email protected]>
closes #1634