Skip to content
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

Closed
chibimi opened this issue Jun 20, 2017 · 6 comments
Closed

tracer: issues with span.buffer #83

chibimi opened this issue Jun 20, 2017 · 6 comments
Labels
bug unintended behavior that has to be fixed

Comments

@chibimi
Copy link
Contributor

chibimi commented Jun 20, 2017

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 ?

@fromz
Copy link

fromz commented Oct 4, 2017

This just bit me now. Did you find a workaround?

@chibimi
Copy link
Contributor Author

chibimi commented Oct 4, 2017

No we haven't put much work into this, we locked the dependency to the commit before the change.

@palazzem palazzem added the bug unintended behavior that has to be fixed label Nov 8, 2017
@palazzem
Copy link
Contributor

palazzem commented Nov 8, 2017

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.

@gbbr gbbr changed the title Issues with span.buffer tracer: issues with span.buffer Jan 17, 2018
@gbbr
Copy link
Contributor

gbbr commented Jan 29, 2018

@chibimi @fromz I'd love to get your help on fixing this issue. Are you still encountering this issue?
If yes, can you help me better understand the problem? I'm new to the project but I can see that we've recently added OpenTracing support. Does the problem still occur when you use our implementation of it?

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?

@chibimi
Copy link
Contributor Author

chibimi commented Jan 29, 2018

Hello. Your open tracing implementation did the trick for us.

@gbbr
Copy link
Contributor

gbbr commented Jan 29, 2018

Good to hear! In that case I'm closing this one.

@gbbr gbbr closed this as completed Jan 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug unintended behavior that has to be fixed
Projects
None yet
Development

No branches or pull requests

4 participants