workbenchdev / workbenchdev/Workbench
Rust: Workbench reads user "rustc-wrapper" configuration, leading to launch issues
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 844
- Forks
- 91
- Avg merge
- 7h 12m
- Merged PRs (30d)
- 1
Description
At the moment it seems that the cargo process launched through Workbench to build the Rust demos reads the user's ~/.cargo/config file.
If Workbench is running in a Flatpak it still reads this file. This can lead to issues if a rustc-wrapper is defined. In that case Workbench/Cargo will launch that wrapper instead. However since it is trying to launch it in the Flatpak sandbox, this will most likely fail due to missing libraries.
Other configuration values may cause similiar issues. It may just be best to keep this sandboxed and don't read ~/.cargo/config if Workbench is running as a Flatpak.
Contributor guide
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 tracing the cargo process Workbench launches to build Rust demos when running as a Flatpak, then inspect how ~/.cargo/config is discovered. Done means Flatpak launches no longer read the user's Cargo configuration, so values such as rustc-wrapper cannot cause sandbox launch failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100