Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#8,025 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
68/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
devtools

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
79.5k
Forks
6.9k
Merge medio
2 d 13 h
PR fusionados (30 d)
41

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de coder/code-server

Todos los issues de coder/code-server

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.