-
Notifications
You must be signed in to change notification settings - Fork 2
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
don't error if network down? #4
Comments
https://github.com/unhammer/build-status/tree/async fixes this by making it all async |
That's a bad error message that's caused by a failing
What's so invasive about it? I think it's important for one to know that a network error is preventing the build status from being updated.
In this context
I think async is the way to go in general, regardless of this error. I'll take a look at your branch shortly. |
Emacs tells me
Failed to update status for /tmp/foo: HTTP/1\.[01] \([0-9]\{3\}\)
whenever I open my laptop, since there's a slight delay until wifi connects. I don't think this calls for an something as invasive as anerror
(which shows even if you haven't looked at a CI-tracked project in hours). How about a special((string= status "status unavailable") (build-status--propertize "?" status))
or something like that?The text was updated successfully, but these errors were encountered: