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

Unsaved editor comes back after "Don't Save" when switching between Windows and macOS browsers

Aperta
  • Qualcosa non va?
#8,025 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
68/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
devtools

Direzione di ricerca

Start in src/vs/workbench/services/workingCopy/common/workingCopyBackupService.ts, especially hashPath and the backup deletion flow. Reproduce the Windows-to-macOS browser sequence and compare fsPath with resource.path for the untitled editor. Done means choosing "Don't Save" removes the existing backup and the editor does not return after reload or restart.

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

Descrizione

bug triage
Is there an existing issue for this?
  • I have searched the existing issues
OS/Web Information
  • Web Browser: Chrome (Windows user agent), Edge 153 (macOS user agent)
  • Local OS: Windows, macOS
  • Remote OS: Ubuntu 24.04
  • Remote Architecture: amd64
  • code-server --version: 4.117.0 ddeb0a3de0321412c0633dffa85d35770005ae0f with Code 1.117.0
Steps to Reproduce
  1. From a Windows browser, run this in the terminal (the file doesn't exist): /app/code-server/lib/vscode/bin/remote-cli/code-server --reuse-window /home/user/project/notes.txt. An untitled editor opens, and a backup is written to User/Backups/<workspace>/untitled/-dd15b27.
  2. Close the browser tab.
  3. Open code-server from a macOS browser. The editor is restored.
  4. Close it and pick "Don't Save".
  5. Reload. It's back, and untitled/-dd15b27 is still there.
Expected

The editor stays closed and the backup is deleted.

Actual

macOS tries to delete untitled/142ac6d3, which doesn't exist. The Windows backup stays, so the editor reopens on every load, even after restarting code-server. Closing it from Windows works.

Logs
None.
Screenshot/Video

No response

Does this bug reproduce in native VS Code?

This cannot be tested in native VS Code

Does this bug reproduce in VS Code web?

I did not test VS Code web

Does this bug reproduce in GitHub Codespaces?

I did not test GitHub Codespaces

Are you accessing code-server over a secure context?
  • I am using a secure context.
Notes

The backup file name is a hash of fsPath (hashPath in src/vs/workbench/services/workingCopy/common/workingCopyBackupService.ts). In the browser, fsPath uses backslashes on Windows and forward slashes everywhere else, so the same file gets a different backup name depending on the client:

  • \home\user\project\notes.txt hashes to -dd15b27
  • /home/user/project/notes.txt hashes to 142ac6d3

Hashing resource.path for untitled files would fix it, though backups already written with backslash names would still need cleaning up. It's still like this on VS Code main, and none of the patches in 4.139.1 touch it.

Lingua principale
TypeScript
Stelle
79.5k
Fork
6.9k
Merge medio
2g 13h
PR unite (30g)
41

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 coder/code-server

Tutte le issue di coder/code-server

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.