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

Mysql 21.0.2 incompatible with poem-openapi 1.0.31 #100

Closed
Christoph-AK opened this issue Nov 30, 2021 · 4 comments
Closed

Mysql 21.0.2 incompatible with poem-openapi 1.0.31 #100

Christoph-AK opened this issue Nov 30, 2021 · 4 comments
Labels
bug Something isn't working

Comments

@Christoph-AK
Copy link
Contributor

Hey there,
I would like to use Poem with Mysql, but they seem to be using incompatible bitvec / funty versions. On build I get a error[E0034]: multiple applicable items in scope --> C:\Users\local\.cargo\registry\src\github.com-1ecc6299db9ec823\bitvec-0.19.4\src\field.rs:307:25.

This problem seems to be known in funty and can apparently be solved by updating all dependencies to funty 2.0.0 (or at least the same version.) Unfortunately it is nested quite deeply in the dependencies.

Example Toml, full build output, and cargo tree output uploaded here: https://gist.github.com/Christoph-AK/366e6c39c24976d5bf48064e658b6670

Can this be solved from this crate?

MySQL Issue: blackbeam/rust-mysql-simple#300

@sunli829
Copy link
Collaborator

Have you enabled the staticfiles or template feature?

@Christoph-AK
Copy link
Contributor Author

Not explicitly, as per the cargo.toml in the gist.
Are they included in default?
Is either likely to impact this problem?

@sunli829
Copy link
Collaborator

Please upgrade to v1.0.33, it removes akasma from dependencies.

@Christoph-AK
Copy link
Contributor Author

Wow, thanks for looking into it so quickly! My projects now build successfully, thank you! And sorry for the inconvenience and having to rip the templating out. This is such an annoying problem which normally shouldn't happen in the first place, but afaik funty screwed up their semantic versioning or something like that...

@sunli829 sunli829 closed this as completed Dec 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants