microsoft / microsoft/vscode-black-formatter
Black permission errors
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 196
- Forks
- 49
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 7
Description
## Diagnostic Data
- Python version (& distribution if applicable, e.g., Anaconda): 3.12.3
- Type of virtual environment used (e.g., conda, venv, virtualenv, etc.): venv
- Operating system (and version): Ubuntu 24.04
- Version of tool extension you are using: 2026.4.0
## Behaviour
### Expected Behavior
Extension works
### Actual Behavior
Extension fails with ./venv permission errors
## Reproduction Steps:
## Logs:
Click here for detailed logs
```
2026-05-06 08:42:17.852 [error] Server: Start failed: Launching server using command **REDACTED**/venv failed. Error: spawn **REDACTED**/venv EACCES
```
## Outcome When Attempting Debugging Steps:
Did running it from the command line work? Yes
## Extra Details
Version 2025.2.0 works without problems.
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 with the Black Formatter extension's server launch path and the log showing spawn of the project's ./venv failing with EACCES. Reproduce on Ubuntu 24.04 with Python 3.12.3, compare extension versions 2025.2.0 and 2026.4.0, and verify that the extension launches successfully while the command-line invocation continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100