Update opentracing dependency to 0.5.0 #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have updated OpenTracing dependencies to
0.5.0.OpenTracing API has changed since version
0.3.2- you can check Git diff but these are the most notable changes:Tracer#start_active_span- returnTest::Scopeand adds this scope to ScopeManager's stackTracer#start_spancan now accepts blockTest::ScopeManager- scope manager keeps track of active span (with stack) tracer can access it withTracer#scope_managerTest::Scope- scope encapsulate spanTracer#active_span- now returns active span - top ofScopeStackSpan#logis now depracated in favour ofSpan#log_kvI have added some useful public method/accessors to each new class. and also references attribute to
Test::Spanto be compatible with API.These new changes should not break the basic idea of this tracer to record all spans in memory. You can now also inspect the current scope stack of the tracer.
The new parts are heavily influenced by Jaeger ruby client.
Please take a look if the tests are sufficient 📗
Refs #19