microsoft / microsoft/vscode-dotnettools
[BUG] Launch fails if extension is installed in readonly filesystem
Open
@AArnott is already working on this.
Since Aug 31, 2023.
area-extensionmanagement
enhancement
- Dominant language
- No language data
- Stars
- 321
- Forks
- 54
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 2
Description
Describe the Issue
If the extension is installed in a read-only FS (as happens in NixOS), the launch fails for 2 reasons:
- The cache directory is set up in the extension directory (which is read-only);
- The extension attempts to chmod the binaries (which are read-only).
I have implemented a fix in the build script for my installation however this would be best solved upstream.
Steps To Reproduce
- Install a Linux distro where .NET is installed in a read-only FS (e.g. NixOS)
- Install the extension (and patch the binaries if you're on NixOS)
- Have the extension fail with "unable to chmod files" and "unable to set up cache directory"
Expected Behavior
Extension detects it is in a read-only FS and makes the appropriate adjustments.
Environment Information
- OS: NixOS 23.11.20230825.5690c42
- VSCode Version: 1.81.1
- Extension Version: 0.4.6
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.
Assessment
This issue has not been assessed yet.