Skip to content

query_map version mismatch #471

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

Closed
ezracelli opened this issue May 5, 2022 · 3 comments
Closed

query_map version mismatch #471

ezracelli opened this issue May 5, 2022 · 3 comments

Comments

@ezracelli
Copy link

Hello! It seems that aws_lambda_events has upgraded to query_map@^0.5. As lambda_http depends on [email protected], I'm getting a host of identical compile errors:

error[E0308]: mismatched types
  --> /$HOME/.cargo/registry/src/gb.xjqchip.workers.dev-1ecc6299db9ec823/lambda_http-0.5.1/src/request.rs:87:42
   |
87 |         .extension(QueryStringParameters(ag.query_string_parameters))
   |                                          ^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `QueryMap`, found struct `query_map::QueryMap`
   |
   = note: perhaps two different versions of crate `query_map` are being used?

Cargo.toml:

[package]
name = "xxx"
version = "0.1.0"
edition = "2021"

[dependencies]
lambda_http = "0.5.1"
tokio = { version = "1.18.1", features = ["macros"] }

cargo tree output:

$ cargo tree -i query_map
error: There are multiple `query_map` packages in your project, and the specification `query_map` is ambiguous.
Please re-run this command with `-p <spec>` where `<spec>` is one of the following:
  query_map:0.4.0
  query_map:0.5.0

$ cargo tree -i query_map:0.4.0
query_map v0.4.0
└── lambda_http v0.5.1
    └── xxx v0.1.0 (/$HOME/code/xxx)

$ cargo tree -i query_map:0.5.0
query_map v0.5.0
└── aws_lambda_events v0.6.3
    └── lambda_http v0.5.1
        └── xxx v0.1.0 (/$HOME/code/xxx)
@ezracelli
Copy link
Author

Ah, I see this will be resolved by #469 !

@calavera
Copy link
Contributor

calavera commented May 5, 2022

yeah, sorry about that 🤕

@calavera
Copy link
Contributor

calavera commented May 5, 2022

fixed

@calavera calavera closed this as completed May 5, 2022
calavera added a commit that referenced this issue May 6, 2022
If you already have a version of aws_lambda_events in your project, and you update lambda_http, the events package's version might not be updated. This can cause compilation issues like the ones we saw in #471. With this change, the events package will be update with new patch versions, which should prevent issues like that from happening.
calavera added a commit that referenced this issue May 9, 2022
If you already have a version of aws_lambda_events in your project, and you update lambda_http, the events package's version might not be updated. This can cause compilation issues like the ones we saw in #471. With this change, the events package will be update with new patch versions, which should prevent issues like that from happening.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants