-
-
Notifications
You must be signed in to change notification settings - Fork 88
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
Cargo.lock does not exist, unable to build with the standard library #411
Comments
Yep - I've been looking into this for the last hour. I rebuilt a previously successful snapshot of my code - the previously successful one now fails. The version of super_native_extensions does not change between the two - lending weight to it being a change in a dependency. And here you see the error in today's build of the previously successful code |
Even though my active toolchain in |
@adil192 - yep - sounds like it to me. Looks like your failing build is running under user account "runneradmin", is that the user account you used to run (BTW I've never done anything with Rust before... so I'm just applying some common sense in the hopes it helps - all while I'm trying to blindly solve my failing build in Azure Pipelines) |
Looks like the latest nightly rust-src component is broken :-/. |
For anyone else coming across this thread, who is using CI such as Azure Pipelines... The super_native_extensions package will download pre-built Rust binaries during build - hard-coded to use the nightly channel. I've worked around this issue in Azure Pipelines by forking the tag https://github.com/Adam-Langley/super_native_extensions/tree/defect/should-depend-on-rust-stable You can use it in your Flutter projects by overriding the dependency:
|
Note, 0.8.19 has been published earlier today. |
Thank you @knopp - great work on a fast turnaround. Do you know whether this change in Rust is a bug, or intended breaking behavior? Interestingly, I see in the Rust docs, they recommend any dependent CI build stable, and a future release channel (beta?) to catch breaking changes with enough time to rectify. Thanks again |
This is definitely a Rust bug. Super_native_extensions used rust nightly to produce release build since it can achieve slightly smaller binaries when rebuilding the standard library with panic=abort (that requires a nightly flag), unfortunately Rust nightly is too problematic to rely on by default. |
Thanks @knopp For anyone else who has cloned my fork - I'll leave it up for another day or so before deleting it. The latest release (0.8.19) fixes the issue. |
My GitHub Actions builds have all failed with my latest release with this error on Linux...
...and the same error on Windows etc...
Maybe this is just an issue with the latest rust nightly, since
the build succeeds on my local machineUpdate: The build fails on my local machine after running
rustup update
which updated rustc from 2024-02-04 to 2024-07-21 (stable) and 2024-08-07 (nightly)The text was updated successfully, but these errors were encountered: