Carlos Alberto Cortez

Hey @CodingFabian Did the reason given above sounds right to you? Let me know ;) @yurishkuro @opentracing/opentracing-java-maintainers Opinion on this?

Hey @adriancole thanks for the feedback. I think that's a very valid point, and the important question here is whether there is a pattern that *requires* the `Scope` to be...

Hey @cwe1ss thanks for the feedback, definitely appreaciated ;) Sounds like we should cook such example for the `testbed` to show that we would need `ScopeManager.active()` in such scenario, to...

Hey everybody, So, trying to move on with this topic, after reading the entire thread again, these are my impressions: * Having a `Scope` instance around **can definitely** be helpful,...

Hey everybody, We would like to have a Cross-Language group call on July 13th (next week) and discuss this item as part of it. Please let me know if you...

@felixbarny I think the case @cwe1ss pointed out some time ago still stands: > I need ScopeManager.active in C# to access the current Scope in scenarios where the library/framework I'd...

Hey @sjoerdtalsma > The close from anywhere is problematic. It should be controlled by the one activating the scope. I think this could be easily 'enforced' by indeed not exposing...

Hey @adriancole > I'm not sure why there is a concept of removing active scope in favor of span.. why this is somehow experimental. This was in use in brave...

Hey @adriancole Sorry, had been busy doing other work ;) So the plan is to work tomorrow on updating the PR for #291 and have something ready for testing soon.

Hey all, FYI: we will be postponing this change, and will release OT 2.0 today/tomorrow (Tuesday, July 10th). We will iterate and will get proper feedback on the rest of...