Carlos Alberto Cortez

Log an error when Scope.close() is called on the incorrect object.

2

A few users have complained about not getting any warning when closing a non-active `Scope`, so this PR tries to do a simple warning. (Prior-art wise, grpc's Context implementation does...

0.32.0 Release

47

This issue tracks the Release Candidate iterations towards the the new 0.32 API for OpenTracing-Java. **RC Branch**: https://github.com/opentracing/opentracing-java/tree/v0.32.0 ## Current Status * **Trace Identifiers** have been added (`SpanContext.toTraceId()` and `SpanContext.toSpanId()`)....

Binary support design

4

A pair of previous PR have shown both the need to have a better Binary support than the one we have now, as well as the need to have a...

Rename start_active_span() to start_active_scope().

4

For your consideration ;) @tedsuo @yurishkuro @palazzem @pglombardo @indrekj

Finishing Span on close

1

I'm opening this issue as I'm curious on whether we should adopt the (now merged) OT Java PR for deprecating finishing `Span`s upon `Scope.close()`. ### Problem For OT Java, finishing...

Set the scope_manager RFC to Test.

4

Initial take on the `ScopeManager` RFC. Notes: * Used 'thread or execution unit' in order to abstract things such as coroutines. * Mentioned `Scope`s are not thread-safe. * Mentioned the...

Add clarification for Span under multithreading scenarios.

10

# Multithreading Span usage. **Current State:** Draft **Author:** [carlosalberto](https://github.com/carlosalberto) In the OpenTracing specification, there is no mention of **Span** behavior under multithreaded applications, nor clarification of any thread-safety requirement. This...

Allow to have the app set late for FlaskTracing.

8

Addresses #22

Support BINARY format

4

As per [this](https://github.com/opentracing-contrib/java-grpc/blob/master/src/main/java/io/opentracing/contrib/grpc/TracingServerInterceptor.java#L278) only `TEXT_MAP` format is supported. I think support for `BINARY` could be added as an option for the user to explicitly specify, and keep `TEXT_MAP` as the...

[OT Shim] Fully support Baggage-only propagation.

1

`Baggage` without a valid `Span` should still be properly propagated in inter-process and in-process operations. This is part of the [OT compatibility section](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/compatibility/opentracing.md) - essentially, the changes are: 1) [ActiveSpan()](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/compatibility/opentracing.md#get-the-active-span):...