-
Notifications
You must be signed in to change notification settings - Fork 517
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
feat(propagation-utils): end pub-sub process span on promise settled #1055
feat(propagation-utils): end pub-sub process span on promise settled #1055
Conversation
@nordfjord thank you for the contribution :) Also please add relevant unit tests for this change. Either in the |
packages/opentelemetry-propagation-utils/src/pubsub-propagation.ts
Outdated
Show resolved
Hide resolved
packages/opentelemetry-propagation-utils/src/pubsub-propagation.ts
Outdated
Show resolved
Hide resolved
packages/opentelemetry-propagation-utils/src/pubsub-propagation.ts
Outdated
Show resolved
Hide resolved
packages/opentelemetry-propagation-utils/src/pubsub-propagation.ts
Outdated
Show resolved
Hide resolved
Thanks for taking the time to review this. I think this is ready for another review now. |
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.
LGTM.
After tests are green this can be merged AFAIC
Thank you for contributing this fix
packages/opentelemetry-propagation-utils/test/pubsub-propagation.test.ts
Show resolved
Hide resolved
When promises are returned from a mapping function we now end the span when that promises resolves rather than doing so immediately. This makes sure that the processing span wraps the entirety of the processing
b745717
to
898eefe
Compare
Not quite sure what was going on but I had to remove the I've verified that |
This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #1055 +/- ##
==========================================
+ Coverage 96.08% 96.20% +0.12%
==========================================
Files 14 26 +12
Lines 893 1529 +636
Branches 191 325 +134
==========================================
+ Hits 858 1471 +613
- Misses 35 58 +23
|
|
When promises are returned from a mapping function we now
end the span when that promises resolves rather than doing
so immediately.
This makes sure that the processing span wraps the entirety of the
processing
Which problem is this PR solving?
An example of what this looks like:
Short description of the changes
Checklist
npm run test-all-versions
for the edited package(s) on the latest commit if applicable.