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
Fix coroutines when running from File > Remote Development
For whatever reason, cs.launch does not work and you have to pass the
modality state. Without this state, they do not launch until after the
remote development window is closed.
Using that from a background process fails, however (something about
only being able to access from EDT), so instead of starting/stopping the
poll there, I just always keep it running in the background (and it just
does nothing when there is no client).
For the re-invoking of the token window, I removed the launch entirely.
Could probably use invokeLater() or something but this seems fine?
Implement backend monitoring
This implements connecting at a lower level, giving us a place to
respawn the backend and reconnect when it goes down, replacing
fullDeployCycle since it does not do that for us.
Closes#392.
Clear recent connections client on error
This will at least give you the opportunity to fix it manually by going
through the new connection flow, until code is added to ask for a token.