Integrate Tokio v1.46.1 task spawn locations #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Tokio PRs tokio-rs/tokio#7417 and tokio-rs/tokio#7440 add the source code locations at which a task was spawned to the
TaskMetastructure provided to the runtime task hook callbacks. These will give us the ability to associate task IDs (which identify a task at runtime) with a source code location in the instrumented program, which is going to make everything a lot easier. This PR picks up those changes and updates the minimum Tokio dependency to 1.46.1.Closes #1