You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mismatched types http::Request<lambda_http::Body> and Request<Body> have similar names, but are actually distinct types
perhaps two different versions of crate http are being used?
Expected Behavior
SDK version alignment
Current Behavior
Forced to use the old version 0.2
Reproduction Steps
Use in the same solution:
lambda_runtime 0.9
aws-sigv4 = "1.1.2"
Possible Solution
This should not even be a solution but it is the only thing right now to make it work
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.
Describe the bug
As with other issues #1041 there is an incompatibility around the SDK
The Lambda runtime, for example:
https://github.com/awslabs/aws-lambda-rust-runtime/blob/main/Cargo.toml
It is using
http = "1.0"
and this has the effect:mismatched types
http::Request<lambda_http::Body>
andRequest<Body>
have similar names, but are actually distinct typesperhaps two different versions of crate
http
are being used?Expected Behavior
SDK version alignment
Current Behavior
Forced to use the old version 0.2
Reproduction Steps
Use in the same solution:
lambda_runtime 0.9
aws-sigv4 = "1.1.2"
Possible Solution
This should not even be a solution but it is the only thing right now to make it work
http = "0.2"
http_v1 = { version = "1.0.0", package = "http" }
Additional Information/Context
No response
Version
Environment details (OS name and version, etc.)
All
Logs
No response
The text was updated successfully, but these errors were encountered: