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.
Every once in a while I run into a situation where the server is either
dead or just misbehaving for whatever reason. Since tide tends to send
a lot of messages to the server, this leads to an annoying state where
it keeps barfing over and over again.
This avoids throwing the no server error if it was just thrown.
I think that there are other situations where things get overly
annoying: I think that there are either other similar errors, and/or
other situations that lead to excessive nagging. If so, then more
work will be needed, but I wanted to put it out now to see if
there's any opinions about doing this.