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

fix error span.finish() call when already called. #6

Merged

Conversation

rockrotem
Copy link
Contributor

No description provided.

@dekelev
Copy link
Owner

dekelev commented Oct 29, 2020

I prefer not to use an internal property (_duration) of a peer-dependency (opentracing) to detect if a span is finished or not.

If the issue is reproducible, then it might be easier to just search for a bug in the flow that can lead to this "span already finished" error.

@dekelev dekelev merged commit aa84bfa into dekelev:master Nov 10, 2020
@dekelev
Copy link
Owner

dekelev commented Nov 10, 2020

Added this test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants