Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Windows sandbox: concurrent commands run out of drive letters

Open
  • Is something wrong?
#177 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
desktop, devtools

Research direction

Start with win.rs:84-103 and trace the mapping lifecycle at win.rs:1626,1636,1890; the report says mappings stay allocated for the run, including background commands. Review the journal and existing tests for Windows drive allocation and cleanup. Done means concurrent commands no longer exhaust available letters, existing user mappings are skipped, and the error or behavior addresses the Explorer drive clutter described.

Written by the indexing model from the issue text.

Description

bug platform: windows priority: low severity: medium

Found in the 2026-10-07 code review (traced through the code; the threshold depends on the user's existing mappings).

Problem

DriveMapping::reserve (win.rs:84-103) uses letters P–Z only. Each run holds a project drive and a temp drive, plus a toolchain drive when toolchains are staged (win.rs:1626,1636,1890), for its whole life, including background commands. Letters the user mapped in that range reduce the pool further. About 4–5 concurrent background commands use it up, and the next command fails with "no drive letter is available for the sandbox working directory". The mappings also show up as extra drives in Explorer.

Fix

  • Share one project-drive mapping per project, reference-counted in the journal.
  • Put temp under the project or toolchain drive instead of giving it its own letter.
  • Extend the range downward and skip letters already in use.
  • At minimum, say in the error how many letters are in use by Patch.
Dominant language
TypeScript
Stars
2
Forks
2
Avg merge
5h 28m
Merged PRs (30d)
24

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PierrunoYT/patch

All issues in PierrunoYT/patch

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.