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

introduce a ConnectionTracingID type for the ConnectionTracingKey #4400

Merged
merged 1 commit into from
Apr 2, 2024

Conversation

marten-seemann
Copy link
Member

@marten-seemann marten-seemann commented Apr 1, 2024

This is a breaking API change. Unfortunately, context values are not strongly typed, so users will have have to take care to change their type assertions.

This is a breaking API change. Unfortunately, context values are not
strongly typed, so users will have have to take to change their type
assertions.
Copy link

codecov bot commented Apr 1, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.90%. Comparing base (18d6d29) to head (32f32df).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #4400   +/-   ##
=======================================
  Coverage   84.90%   84.90%           
=======================================
  Files         152      152           
  Lines       14342    14342           
=======================================
  Hits        12177    12177           
  Misses       1666     1666           
  Partials      499      499           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Comment on lines 60 to +63
var ConnectionTracingKey = connTracingCtxKey{}

// ConnectionTracingID is the type of the context value saved under the ConnectionTracingKey.
type ConnectionTracingID uint64
Copy link
Member Author

Choose a reason for hiding this comment

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

I'm not really happy with the name. Tracing is an overloaded term, and we already used it for event tracer.

Any suggestions for a better name?

Copy link
Collaborator

Choose a reason for hiding this comment

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

I guess this is okay.
Other ideas that come to my mind are:

ConnectionTrackingID
ConnectionSeqID (as the id is sequential)
ConnectionName (used as a name for this connection in tracking)

Copy link
Member Author

Choose a reason for hiding this comment

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

Thank you!

@marten-seemann marten-seemann merged commit 27a06f3 into master Apr 2, 2024
64 of 65 checks passed
@marten-seemann marten-seemann deleted the connection-tracing-id branch April 2, 2024 04:24
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

2 participants