Closed Proxxa closed 2 weeks ago
If this is not a bug and is instead a limitation enforced by Shuttle, I apologize. It is written nowhere that the nightly channel is not supported, but this is something that I'd like to do for the sake of getting information at compile time rather than runtime.
Hey @Proxxa! This is currently a limitation enforced by Shuttle, all users services run and build on the same container image which is pinned to 1.70 (usually the latest stable). We are working on a new service for building users services, where each one will get its own image. For this builder, we plan to allow the user to set some config for which Rust version they'd like to use, as well as native dependencies etc.
You are right that this current version cap is not mentioned anywhere, that should definitely be resolved, I'll add it to the FAQ in the docs for starters!
Hi @oddgrd ! Thanks for the quick response! While it's sad, this does make me look forward to future updates to shuttle. Should I close this issue, or should I keep it open as a way to track nightly support/adding this to the FAQ?
I think we can change this to a feature request, something like "allow specifying rust toolchain/version", and leave it open.
Changed the title. Unfortunately, I don't believe I can edit the label myself. Supposedly, that requires triage repo access.
Thanks!
Prebuild hook script (experimental feature) can now be used to install a custom toolchain on shuttle.dev: https://docs.shuttle.dev/docs/builds#experimental-hook-scripts
What happened?
In deployment, Shuttle fails to build my project because I rely on unstable features for a proc_macro that I use. In particular, I use
proc_macro_span
andproc_macro_internals
to get the path to the calling macro. This is because I want this macro to act likeinclude_str!
and prepend the file contents with a timestamp stating when the file was created.Here is the rust file:
Here is the
Cargo.toml
of this proc_macro library:And here is the
Cargo.toml
of the main project:BOTH directories have a
rust-toolchain.toml
containing the following:Version
v0.22.0
Which operating system(s) are you seeing the problem on?
In deployment
Which CPU architectures are you seeing the problem on?
In deployment
Relevant log output
Duplicate declaration