Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Windows sandbox: share one drive letter per project and drop the separate temp drive

Chiusa
  • Qualcosa non va?
#228 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
18/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust, typescript
Ambito
operating-systems, security

Direzione di ricerca

Start in native/sandbox-helper/src/win.rs, where record.project_drive and record.toolchain_drive are assigned, and in ProjectDrive::create(temporary) to see how each run gets its own letter. Then read the recovery journal code that stores letter and target, and the DDD_EXACT_MATCH_ON_REMOVE removal path. Done means concurrent background commands in one project all run when they outnumber free letters, and forced-termination recovery still removes only abandoned mappings. Confirm with the real-helper test the issue asks for.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement platform: windows priority: low severity: low

Follow-up to #177.

#177's fix widened the letter range for sandbox drives from P:–Z: to D:–Z:, and made the error say how many Patch commands hold letters. Each run still holds its own letters for its whole life, background commands included:

  • a project drive (record.project_drive, native/sandbox-helper/src/win.rs),
  • a temporary drive (ProjectDrive::create(temporary)),
  • a toolchain drive when toolchains are staged (record.toolchain_drive).

With a few user mappings in D:–Z:, roughly eight to ten concurrent commands still use them all up, and each mapping still shows up as an extra drive in Explorer while it exists.

Proposal

  • Share one project-drive mapping per project, reference-counted through the recovery journal: recovery records already store the exact letter and target, so a new run in the same project can reuse a live mapping and only the last run removes it.
  • Put the temporary folder under the project or toolchain drive instead of giving it its own letter, or reach it by its real path with only its own grant.
  • Keep the exact-match removal (DDD_EXACT_MATCH_ON_REMOVE) so a reused letter is never removed under another run.

Acceptance checks

  • A real-helper test starts more concurrent background commands in one project than there are free letters and all of them run.
  • Forced-termination recovery still removes only abandoned mappings.
Lingua principale
TypeScript
Stelle
2
Fork
2
Merge medio
6h 27m
PR unite (30g)
37

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di PierrunoYT/patch

Tutte le issue di PierrunoYT/patch

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.