rustdesk / rustdesk/rustdesk-server
Github Actions build fails
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10.4k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
I'm sorry if this is something obvious, but whenever I try to build the package I get this:
error: failed to compile cross v0.2.5, intermediate artifacts can be found at C:\Users\RUNNER~1\AppData\Local\Temp\cargo-installWAsoV8.
To reuse those artifacts with a future compilation, set the environment variable CARGO_TARGET_DIR to that path.
Caused by:
failed to parse manifest at C:\Users\runneradmin\.cargo\registry\src\index.crates.io-6f17d22bba15001f\home-0.5.12\Cargo.toml
Caused by:
feature edition2024 is required
The package requires the Cargo feature called `edition2024`, but that feature is not stabilized in this version of Cargo (1.81.0 (2dbb1af80 2024-08-20)).
Consider trying a newer version of Cargo (this may require the nightly release).
See https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#edition-2024 for more information about the status of this feature.
Error: The process 'C:\Users\runneradmin.cargo\bin\cargo.exe' failed with exit code 101****
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the GitHub Actions workflow that installs or invokes Cargo, then check how its Rust and Cargo versions are configured. Reproduce the build failure with Cargo 1.81.0 and identify the toolchain change needed for the dependency requiring the edition2024 feature; done means the workflow completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100