Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make no-server errors less naggy #424

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

elibarzilay
Copy link
Collaborator

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.

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants