Jetbrains Gateway cannot connect after 3.5h IDLE period #148
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vrubezhny
requested review from
adietish and
azatsarynnyy
and removed request for
azatsarynnyy
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #148 +/- ##
======================================
Coverage 0.00% 0.00%
======================================
Files 4 25 +21
Lines 26 990 +964
Branches 0 153 +153
======================================
- Misses 26 990 +964 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
vrubezhny
force-pushed
the
fix-cannot-connect-when-idle
branch
from
3247d8d to
86b4d42
Compare
Fixes eclipse-che/che#23485 Signed-off-by: Victor Rubezhny <[email protected]>
vrubezhny
force-pushed
the
fix-cannot-connect-when-idle
branch
from
86b4d42 to
7dd1828
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the DevSpaces WS isn't started or ready, this PR starts the WS and waits for its readiness before starting the Remote IDE Client:
cold-start_spedup.mp4
In some cases the Remote IDE Server cannot correctly process requests (status/stop) - usually when this happens we have no other option to recover, but the full DevSpaces Pod restart. so. with this PR, the User is asked to restart and if agreed, the DevSpaces Pod gets terminated and then restarted, which in its turn makes the Remote IDE server to correctly start:
remote-ide-not-responsive_spedup.mp4
Fixes eclipse-che/che#23485