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
Within the new Gateway, an open workspace is maintained as an active connection. This means that a workspace is essentially 'started', even if one isn't actually making use of it. As a result, workspace activity is inaccurate and features like autostart/autostop are compromised.
We should find a way to spawn SSH connections only on click or selection.
Hopefully, this can be done with JetBrains' existing API; if not, we should consider reimplementing the environment list from scratch. See #423 for additional detail on the environment list; there is a discussion about re-implementing from scratch in that ticket, as well.
The text was updated successfully, but these errors were encountered:
Within the new Gateway, an open workspace is maintained as an active connection. This means that a workspace is essentially 'started', even if one isn't actually making use of it. As a result, workspace activity is inaccurate and features like autostart/autostop are compromised.
We should find a way to spawn SSH connections only on click or selection.
Hopefully, this can be done with JetBrains' existing API; if not, we should consider reimplementing the environment list from scratch. See #423 for additional detail on the environment list; there is a discussion about re-implementing from scratch in that ticket, as well.
The text was updated successfully, but these errors were encountered: