-
-
Notifications
You must be signed in to change notification settings - Fork 201
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
Do twice check on HTTP error #310
Comments
This might be more flexible with |
Perhaps this should be implemented upstream. A ticket is open at I am not sure if retry should be in scope for implementing in this project. |
I agree. This is something that Typheous will need to support first. |
@gjtorikian When Typheous will start support it, will HTML proofer do it by default? If not and there will be needed some work, this issue should be left open. |
In theory, yes. HTML-Proofer just blindly passes over the Typheous/Hydra config options. It doesn't do any validation there or extra checks. So if an option is made available for Typheous, passing it through should be fine. |
This issue is closed, but I'm hugely in support of retry parameters. Our builds are consistently failing on travis because of one spurious URL error. |
If so then the issue should be bumped on Typheous, as noted above. This gem depends on that one for external calls. |
HTML proofer sometimes returns this error:
It propably means linked website is hosted on some shitty hosting, so it sometimes not responds to request. But some websites do it often and it causes false alarm.
Feature request: If there is error on remote site, what about to try it once again a few seconds ago? If second try will be ok, there should not be error on output, so tests will pass.
The text was updated successfully, but these errors were encountered: