https://linen.dev logo
The filename, directory name, or volume label synt...
# help
m
I am getting this error on
cargo shuttle run
k
Would you mind trying with rust 1.66 or 1.65?
m
I actually tried with 1.66
then updated to 1.67
and got the same error
let me try with 1.65
k
I tested it earlier on windows, and for me it worked on 1.65 and 1.66, You might also try a cargo clean and a cargo build after changing toolchain
m
Nope, getting the same on 1.65
a
what happens if you try running shuttle_service at v0.8.0?
just curious since my most recently created project was at v0.8.0 and it seems to compile just fine
k
You could also try with the binary for windows from the release:
It's compiled with 1.65
a
trying the original situation out on my machine now and seeing what happens
ok so, some notes: I got this trying to binstall cargo-shuttle - not sure if it helps you guys at all but here it is:
Copy code
INFO resolve: Resolving package: 'cargo-shuttle'
 WARN Package does not specify repository, cargo-binstall cannot provide default pkg_url for it.
Please ask the upstream to provide it for target x86_64-pc-windows-msvc.
 WARN The package cargo-shuttle v0.9.0 will be installed from source (with cargo)
Do you wish to continue? yes/[no]
ok! so I've tried to update my cargo-shuttle to 0.9 and related deps to 0.9.0, tried messing around with my rustup version, tried going to 1.67 and then back to 1.65, found out mime types weren't working and added the patch to my rust install and everything works now, except for the fact that tokio panics at this:
Copy code
thread 'tokio-runtime-worker' panicked at '[internal exception] blocking task ran twice.', C:\Users\joshu\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-1.22.0\src\runtime\blocking\task.rs:32:14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: Panic occurred in shuttle_service::main`:
not sure if this will help but i did the following and it seemed to fix the issue: - use
rustup default 1.65
to set rust version to 1.65 - reinstall
cargo-shuttle
(from
cargo install cargo-shuttle
- the binary seems to be broken for windows so it should probably be avoided for now) - try using
cargo shuttle run
, if you get some error about
mime_guess
, use this patch in your Cargo.toml:
Copy code
[patch.crates-io.mime_guess]
git="https://github.com/NathanSWard/mime_guess.git"
branch="platform-path-separators"
-
cargo shuttle run
should now work properly I'm on win11 so not entirely sure if this will work with other versions of windows, but it seems to be compatible with shuttle 0.9.0 stuff
m
I will try asap 🫡
I am also on win11
a
lmk how it goes, not sure what else we can try if it doesn't work after that though
m
Just tried with 0.9.0 on a fresh project and latest cli and it doesn't work
downgrading shouldn't be the solution anyway
one thing that bothers me is this:
I am 100% that \\?\ is causing issues
I tried making the same code as rustversion with a wrong path so it failed, and you can see there is no \\\?\
I also tried with rustversion on a dummy project and it worked, so... I am pretty sure the error is because of \\?\
I took a look at the shuttle cli code, but well, there is too much code so I don't know where the problem is
a
it looks like from what i've googled,
\\?\
is just to denote an extended path length and doesn't actually mean anything
m
Weird
Idk then
a
i think this appears to be related to a cargo issue since there was a cargo meta-issue a while ago about extra long path names
m
ah wait
I think I know
look at this
it doesn't translate / to \
so the /version stays like /version
a
yea, not really ideal
it appears that this is an error with path canonicalisation and not anything that shuttle itself is doing
i think this might be relevant? but not sure https://github.com/rust-lang/rust/issues/42869
I tried stripping the canonicalised part away (the
\\?\
) and it returns
'internal error: entered unreachable code: unexpected stage'
, so i mean i guess that's progress?
12 Views