-
Notifications
You must be signed in to change notification settings - Fork 42
Call span.end() in the happy path in withSpan #33
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
Conversation
Can one of the admins verify this patch? |
4 similar comments
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
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 taking this on, @JensAyton! 👍 LGTM, just some minor nitpicks to clean up the assertions.
Sounds good to me. Would you mind adding this as well? |
@swift-server-bot add to whitelist |
Let me merge this and let's do
in a follow up please @JensAyton ? Thanks a lot! |
Updates behaviour of
withSpan
to match documentation.I would consider also making the
context
form ofwithSpan
(which is untested) call into thebaggage
variant.Fixes #30