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
Jetbrains Gateway creates many ssh sessions to connect to coder workspaces. After some digging into the underlying behavior, I've noticed that Jetbrains Gateway plugin will create ssh sessions when opening an IDE to a workspace and upon closing the IDE the ssh connections will be held open until the gateway client is closed.
After opening and closing the IDE to a workspace you can see the ssh session open still:
Because these are held open they will continue to bump workspace activity indefinitely despite no active IDE session to the workspace. While collaborating with @code-asher we were able to isolate this behavior down to to Jetbrains Gateway (not our plugin code) and @code-asher is filing a bug with Jetbrains directly with our reproduction steps. We've ruled out that this could be related to coder ssh by reproducing this issue with a regular ssh command in the ProxyCommand config and still seeing the same issue.
In legacy workspace activity tracking we solved this by tracking the port-forward session at the agent ssh server and this is accurately tracking usage today. In the new workspace activity system this behavior is a problem because we rely on the client sending us activity updates, and if the client is incorrectly holding open ssh connections for hours on end we can't tell from our side that this activity update is invalid and we will continue to record activity to the workspace long after the IDE has been closed.
The text was updated successfully, but these errors were encountered:
Jetbrains Gateway creates many ssh sessions to connect to coder workspaces. After some digging into the underlying behavior, I've noticed that Jetbrains Gateway plugin will create ssh sessions when opening an IDE to a workspace and upon closing the IDE the ssh connections will be held open until the gateway client is closed.
After opening and closing the IDE to a workspace you can see the ssh session open still:
Because these are held open they will continue to bump workspace activity indefinitely despite no active IDE session to the workspace. While collaborating with @code-asher we were able to isolate this behavior down to to Jetbrains Gateway (not our plugin code) and @code-asher is filing a bug with Jetbrains directly with our reproduction steps. We've ruled out that this could be related to
coder ssh
by reproducing this issue with a regular ssh command in the ProxyCommand config and still seeing the same issue.In legacy workspace activity tracking we solved this by tracking the port-forward session at the agent ssh server and this is accurately tracking usage today. In the new workspace activity system this behavior is a problem because we rely on the client sending us activity updates, and if the client is incorrectly holding open ssh connections for hours on end we can't tell from our side that this activity update is invalid and we will continue to record activity to the workspace long after the IDE has been closed.
The text was updated successfully, but these errors were encountered: