microsoft / microsoft/vscode-remote-release
SSE connections wont close ( golang )
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Is there an existing issue for this bug?
- I have searched the existing open issues and found none that apply.
- If I find any issue of interest that is related or closed, I will included a link to it in this issue.
Required Troubleshooting Steps
- I have read and performed the troubleshooting steps
- I have tried both values of the
remote.SSH.useLocalServersetting - My issue was not covered in the Tips and Tricks linked from the Troubleshooting Wiki.
- I will include a complete copy of my Remote - SSH logs by running Remote-SSH: Show Log in the command palette or from View > Output in the menu bar
[Optional] Diagnose with Copilot
I asked @remote-ssh but it did not help
In step 2 of the troubleshooting wiki, what was the result of running the generated SSH command verbatim outside of VS Code?
I COULD successfully SSH to the remote machine with the generated SSH command
Remote-SSH Log
Remote-SSH Log
no any output logs
Expected Behavior
close SSE / connection on remote server via forwarded port to localhost
Actual Behavior
SSE connections keeps growing
Steps To Reproduce
connect to remote linux machine
clone repo https://github.com/blinkinglight/vscoderemotesshbug and run go program
forward port 1234
open http://localhost:1234/sse you should see stream in browser, and in vscode terminal - Sent SSE message
close browser tab
in vscode terminal you should see: Successfully closed SSE connection
and stream of "Sent SSE message" should stop
Anything else?
latest stable vscode ( not insiders ) with latest remote ssh pre-release extesion ( same problem with stable )
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Clone and run the linked blinkinglight/vscoderemotesshbug repository, then reproduce the SSE request through Remote-SSH port forwarding on port 1234. Compare the browser disconnect with the Go server's expected closure message and inspect how the forwarded connection handles disconnects; done when closing the tab stops the stream and the server reports a closed SSE connection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux, vscode
- Domain
- devtools, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100