coder / coder/code-server

Code server disconnects after browser inactivity for a while

Abierto
#7,016 9 comentarios 1 reacción 0 asignados Ver en GitHub
bug triage
Lenguaje dominante
TypeScript
Estrellas
79.3k
Forks
6.8k
Merge medio
2 d 6 h
PR fusionados (30 d)
41

Descripción

### Is there an existing issue for this?

- [X] I have searched the existing issues

### OS/Web Information

- Web Browser: Chrome, Firefox
- Local OS: macOS, Windows
- Remote OS: Amazon linux 2 (Sagemaker)
- Remote Architecture: x86_64 GNU/Linux
- `code-server --version`: code-server: v4.16.1, Code: 1.80.2

### Steps to Reproduce

1. launch code server on Sagemaker notebook instances
2. Connect from local machine using Chrome, or Firefox
3. When the go computer is idle (e.g. in screen saver mode) for a while (the duration is not consistent, but 15min should do), or when the browser is out of focus for a long time, the vscode client page gets disconnected: the file system is no longer responsive (we have a blue clock icon and a horizontal line that scrolls continuously, see screeshot); and the terminal no longer respond also
4. Refreshing the browser page brings the connection back to normal

### Expected

The vscode code client should not be disconnected when the computer has access to internet

### Actual

Vscode client page gets disconneted when computer is idle or when browser is out of focus for a while

### Logs

_No response_

### Screenshot/Video

![vscode-disconnection](https://github.com/user-attachments/assets/41a53ef1-a829-437f-a10a-8cb16624372d)

### Does this bug reproduce in native VS Code?

I did not test native VS Code

### 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

_No response_

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Comienza reproduciendo la desconexión en code-server v4.16.1 en un notebook de SageMaker con Chrome o Firefox después de aproximadamente 15 minutos de inactividad. Inspecciona el comportamiento de la conexión y recopila registros durante el fallo; se considera completado cuando el cliente de VS Code y el terminal siguen respondiendo sin requerir una actualización del navegador.

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

Evaluación

Stack tecnológico
typescript
Área
devtools, web-dev
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
28/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.