Updated futures-rs, tokio, tower and rust #836
Closed
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
- rust nightly-2019-10-04 (Requires new docker image build) - futures alpha.19 - tokio alpha.6 - tower alpha2 Came across this panic in the rust compiler in a PR to follow: rust-lang/rust#64385
sdbondi
force-pushed
the
sb-upgrade-futures-rust
branch
from
c27d47a to
263d7b4
Compare
11 tasks
|
Covered in #837 |
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.
Description
Came across this panic in the rust compiler in #837 :
rust-lang/rust#64385
Motivation and Context
Compilation panics on currently used rust version. Issue: rust-lang/rust#64385
futures-rs and tokio upgrades because tower 0.3.0-alpha.2 uses futures=0.3.0-alpha.19
How Has This Been Tested?
Existing tests pass
Types of changes
Checklist:
developmentbranchcargo-fmt --allbefore pushing