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

Linter returns confusing errors #80

Closed
glauberfc opened this issue May 14, 2019 · 1 comment
Closed

Linter returns confusing errors #80

glauberfc opened this issue May 14, 2019 · 1 comment

Comments

@glauberfc
Copy link

I'm receiving different errors running the linter some times without didn't any change on README.

Screen Shot 2019-05-14 at 7 43 04 PM

@transitive-bullshit
Copy link
Collaborator

This looks related to #50 given that we're doing a best effort to try and detect dead or inaccessible URLs. Aside from the possibility of fluctuations in your connectivity, it's possible the remote host's uptime or response time is also fluctuating.

Our goal is to be as robust as possible against these types of fluctuations, though it will never be possible to be 100% since not even a human testing manually could accurately say whether a given link is fully dead or not.

Please follow-up with your false negative dead URLs in this issue. Any other thoughts on how to improve the robustness of dead link checking is very welcome.

Thanks! 😄

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

No branches or pull requests

3 participants