Cargo build failed due to unresolved import http_body::combinators

[neara]

Bug Report

Version

In Cargo.toml:

aws-config = "0.0.25-alpha"
aws-sdk-cloudfront = "0.0.25-alpha"

Cargo tree:

❯ cargo tree | grep aws-sdk-
│   ├── aws-sdk-sts v0.0.25-alpha
├── aws-sdk-cloudfront v0.0.25-alpha

Platform

Darwin 21.1.0 Darwin Kernel Version 21.1.0: Wed Oct 13 17:33:23 PDT 2021; root:xnu-8019.41.5~1/RELEASE_X86_64 x86_64

Description

In an existing project, I added aws-config and aws-sdk-cloudfront.
Run cargo build -> project is not building anymore with error:

❯ cargo build
   Compiling aws-smithy-http v0.28.0-alpha
error[E0432]: unresolved import `http_body::combinators`
  --> /Users/janedoe/.cargo/registry/src/github.com-1ecc6299db9ec823/aws-smithy-http-0.28.0-alpha/src/byte_stream.rs:98:16
   |
98 | use http_body::combinators::BoxBody;
   |                ^^^^^^^^^^^ could not find `combinators` in `http_body`

error[E0433]: failed to resolve: could not find `combinators` in `http_body`
  --> /Users/janedoe/.cargo/registry/src/github.com-1ecc6299db9ec823/aws-smithy-http-0.28.0-alpha/src/body.rs:46:27
   |
46 | type BoxBody = http_body::combinators::BoxBody<Bytes, Error>;
   |                           ^^^^^^^^^^^ could not find `combinators` in `http_body`

Some errors have detailed explanations: E0432, E0433.
For more information about an error, try `rustc --explain E0432`.
error: could not compile `aws-smithy-http` due to 2 previous errors

[rcoh]

can you please include http-body (or ideally a full) cargo tree output?

[rcoh]

seems like our http-body version is too low (combinators was added in a minor version. smithy-rs#883 fixes)

[neara]

can you please include http-body (or ideally a full) cargo tree output?

❯ cargo tree | grep http-body
│   ├── http-body v0.4.0
│   │   ├── http-body v0.4.0 (*)

[rcoh]

In the meantime, you can fix this by adding an explicit dependency on http-body = 0.4.4 or by running cargo update

[neara]

Excellent, thanks 🙏🏻 Cargo build is work now.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.