Fixes forever stuck spinner in case of docker internal failure#336
Merged
Conversation
Current coverage is 94.91% (diff: 100%)@@ master #336 diff @@
==========================================
Files 90 90
Lines 3799 3799
Methods 0 0
Messages 0 0
Branches 247 247
==========================================
Hits 3606 3606
Misses 133 133
Partials 60 60
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
If the docker server is unavaiable for some reason, we want to stop the spinner anyway. We will get plenty of log on the server, but for now the user should not know.