Pin tokio to LTS release v1.14 #25024
Merged
Conversation
This file contains 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
t-nelson
approved these changes
May 6, 2022
CriesofCarrots
force-pushed
the
v1.9-pin-tokio
branch
from
6444529
to
524b478
Compare
CriesofCarrots
added
the
automerge
mergify
bot
removed
the
automerge
|
automerge label removed due to a CI failure |
CriesofCarrots
added
the
automerge
|
automerge label removed due to a CI failure |
mergify
bot
removed
the
automerge
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.
Problem
The RPC stall problem we are debugging appears when upgrading tokio from v1.15 to v1.16. Currently, our branches do not restrict the tokio minor or patch versions
Summary of Changes
Pin tokio to the the long-term support release v1.14
Inspired by #24644