Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aws-lambda-rust-runtime is using http = "1.0" #1042

Closed
ymwjbxxq opened this issue Jan 14, 2024 · 2 comments
Closed

aws-lambda-rust-runtime is using http = "1.0" #1042

ymwjbxxq opened this issue Jan 14, 2024 · 2 comments
Labels
bug This issue is a bug. duplicate This issue is a duplicate.

Comments

@ymwjbxxq
Copy link

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> 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

http = "0.2"
http_v1 = { version = "1.0.0", package = "http" }

Additional Information/Context

No response

Version

http v0.2.11
http v1.0.0

Environment details (OS name and version, etc.)

All

Logs

No response

@ymwjbxxq ymwjbxxq added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Jan 14, 2024
@jmklix jmklix added duplicate This issue is a duplicate. and removed needs-triage This issue or PR still needs to be triaged. labels Feb 9, 2024
@jmklix
Copy link
Member

jmklix commented Feb 13, 2024

Closing this issue as it is a duplicate of this tracking issue: #977
Please check out the tracking issue for any updates

@jmklix jmklix closed this as completed Feb 13, 2024
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. duplicate This issue is a duplicate.
Projects
None yet
Development

No branches or pull requests

2 participants