-
Notifications
You must be signed in to change notification settings - Fork 225
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
esp-wifi 0.7 does not compile with embedded-svc feature #1817
Comments
The good thing is embedded-svc is totally optional and we have an inherent WiFi API which looks the same - just needs different imports With the (currently configured) version 0.27.1 it compiles fine. Just updating the version to a semver incompatible version is expected to fail. Nevertheless, updating embedded-svc might be a good thing. Also checking the feature in CI is probably something we want. Will change the title of this issue accordingly |
embedded-svc
feature embedded-svc
dependency to 0.28.0
I don't know if I'm missing something, but esp-wifi is currently depending on embedded-svc 0.28 and currently fails to build with the embdded-svc feature enabled, contradicting "with the (currently configured) version 0.27 it compiles fine". Lines 23 to 24 in 14baad4
This is blocking updating esp-mbedtls to the latest versions of the hal crates. |
embedded-svc
dependency to 0.28.0
Oh, sorry for that! I haven't noticed it was changed. You are right - the released 0.7.0 depends on 0.28.0 |
I will publish 0.7.1 soon |
0.7.1 is published, 0.7.0 is yanked now. Thanks for reporting this issue |
Should another issue be made for making sure this doesn't happen again (adding CI coverage for this feature)? |
I think #1693 remotely touches the issue - probably worth a comment there to not forget about this (especially since that issue is planned to be worked on for the upcoming milestone) |
It seems like
esp-wifi
was never updated for esp-rs/embedded-svc#75 when bumping the version number, and there is no CI coverage foresp-wifi
withembedded-svc
.The text was updated successfully, but these errors were encountered: