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

#31 fix server span activation #33

Merged
merged 1 commit into from
Mar 12, 2019
Merged

#31 fix server span activation #33

merged 1 commit into from
Mar 12, 2019

Conversation

malafeev
Copy link
Contributor

No description provided.

Signed-off-by: Sergei Malafeev <sergeymalafeev@gmail.com>
@coveralls
Copy link

Pull Request Test Coverage Report for Build 120

  • 41 of 45 (91.11%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.09%) to 85.762%

Changes Missing Coverage Covered Lines Changed/Added Lines %
src/main/java/io/opentracing/contrib/grpc/ServerTracingInterceptor.java 41 45 91.11%
Totals Coverage Status
Change from base Build 118: 0.09%
Covered Lines: 259
Relevant Lines: 302

💛 - Coveralls

@malafeev malafeev merged commit b5a6e74 into master Mar 12, 2019
@malafeev malafeev deleted the active_server_span branch March 12, 2019 16:22
if (streaming || verbose) {
span.log(ImmutableMap.of("Message received", message));
}
try (Scope ignored = tracer.scopeManager().activate(span, false)) {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Scope ignored should be Scope scope, as it is not actually ignored, try() calls close() on it.

}

@Override
public void onHalfClose() {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure what halfClose means - should the span be finished here?

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.

None yet

3 participants