-
Notifications
You must be signed in to change notification settings - Fork 260
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
Fail to deploy due to incompatible version of rustc #527
Comments
Hey @snylonue, apologies for the delayed response. We have experienced this issue when deploying a few times before, it seems to be caused by crates that have a I also see you are using a git dependency in your manifest, which is not supported by the version of shuttle you are currently using (0.7.2). It is supported by the newly released |
It first occurs when compiling
It is a great improvement. |
Yeah, we've seen this before with |
I have successfully deployed by manually patching the crates with rust-toolchain.toml, which can be served as a temporary fix. |
Ah of course, that's possible now. Good thinking @snylonue, thanks! |
It's breaking shuttle builds, see shuttle-hq/shuttle#527.
The rust-toolchain file in axum-macros is causing issues with shuttle deploys (see shuttle-hq/shuttle#527) so let's just not include it for now.
The rust-toolchain file in axum-macros is causing issues with shuttle deploys (see shuttle-hq/shuttle#527) so let's just not include it for now.
@oddgrd When will the fix get deployed? |
log:
cargo shuttle logs 4857c73c-aef9-4d44-a19a-2895ceca2b3d
environment: both Ubuntu in wsl2 and github actions
project: https://github.com/snylonue/annil-serverless
It works well if I run
cargo shuttle run
, but when runningcargo shuttle deploy
, it complainsfound crate * compiled by an incompatible version of rustc.
, even if I switched to the required rustc(rustc 1.59.0 (9d1b2106e 2022-02-23)
).What confuses me is that shuttle reports the rustc used is
1.63.0
while I have rustc1.65.0
installed.The text was updated successfully, but these errors were encountered: