-
Notifications
You must be signed in to change notification settings - Fork 438
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
tracer: issues with span.buffer #83
Comments
This just bit me now. Did you find a workaround? |
No we haven't put much work into this, we locked the dependency to the commit before the change. |
hello @chibimi! something we can do on our side to help you? By the way, we're going to officially support OpenTracing API in this core library, so the API will be different from what we have now. |
@chibimi @fromz I'd love to get your help on fixing this issue. Are you still encountering this issue? If yes, I'd be more than happy to work together and fix this. It would be nice if I'd be able to write a test to start with. Can you give me more detail on how to reproduce the issue? |
Hello. Your open tracing implementation did the trick for us. |
Good to hear! In that case I'm closing this one. |
Hello
I have the following error "no span buffer" since the recent changes to the lib.
I create childs across services by sending parent info (tradeid, parentid, spanid...) in HTTP headers. (see https://github.com/gchaincl/dd-go-opentracing)
Today the parent's buffer is required to create a child but since it's a private fields it is inaccessible.
Do you think it is possible to add a nil check before span.buffer = parent.bufer in the NewChildSpan func ?
The text was updated successfully, but these errors were encountered: