You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our GitPod workspaces spin up multiple docker containers whose ports are forwarded our local machines, and we use VSCode as our editor. Occasionally, the ports become irresponsive; they hang and eventually our requests timeout.
This happens frequently with Postgres on port 5432, but also sometimes with our rails app at 3000. Strangely, deleting the port from VSCode and adding it back manually fixes this issue in most cases. Sometimes this 'fix' does not resolve the issue, and instead the problem fixes itself after some unknown amount of time.
Steps to reproduce
We are unsure how to exactly reproduce this issue, but it comes up most commonly when:
Switching between git branches
The workspace itself times out and needs to be reopened from the GitPod web UI (note however that this has occurred even in active workspaces)
Workspace affected
No response
Expected behavior
The ports should simply not become irresponsive.
Example repository
No response
Anything else?
The Ports tab where ports can be deleted and added:
The text was updated successfully, but these errors were encountered:
Same issue happens here... no ports available,
blue horizontal cursor keeps moving, like searching/loading ports, but none ever appear.
Have had this issue for a couple of days, not before.
Hey - wanted to leave an update. We have not uploaded logs because #20224 is actually hitting so often that we are not seeing this issue right now. We will send some logs as soon as that other one is fixed.
Bug description
Our GitPod workspaces spin up multiple docker containers whose ports are forwarded our local machines, and we use VSCode as our editor. Occasionally, the ports become irresponsive; they hang and eventually our requests timeout.
This happens frequently with Postgres on port 5432, but also sometimes with our rails app at 3000. Strangely, deleting the port from VSCode and adding it back manually fixes this issue in most cases. Sometimes this 'fix' does not resolve the issue, and instead the problem fixes itself after some unknown amount of time.
Steps to reproduce
We are unsure how to exactly reproduce this issue, but it comes up most commonly when:
Workspace affected
No response
Expected behavior
The ports should simply not become irresponsive.
Example repository
No response
Anything else?
The Ports tab where ports can be deleted and added:
The text was updated successfully, but these errors were encountered: