-
Notifications
You must be signed in to change notification settings - Fork 192
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
Broken Links #331
Comments
The latest breakage is docker. This has already been reported in their github issues 10+ times, so no need to report it again. |
What do you think about adding the ability to specify temporarily-broken sites in an environment variable through the Travis web interface? That would allow us to get builds up-and-running in the short term when things like this happen. |
Interesting idea. I suppose it would be nice for new contributors who are trying to get a green light. Of course, it would make it more effort to find out when links are fixed though. |
Broken links of the day:
htmlproofer 3.4.0 | Error: HTML-Proofer found 2 failures! These pages are up, so no action taken yet. |
google plus seems to have fixed itself. New breakage:
possible candidate for excluding because of ssl errors |
This one's fun:
|
@bmegli The link to http://www.minutebot.com/minuteproducts/base on http://www.ev3dev.org/projects/2016/08/07/Mapping/index.html is broken; that domain no longer seems to exist. What do you want to do to resolve this? |
It looks like Travis might be having networking issues; we're getting lots of inconsistent timeouts: https://travis-ci.org/ev3dev/ev3dev.github.io/builds/213577585 |
Lego has changed the link for mindstorms from http://mindstorms.lego.com to https://lego.com/mindstorms. |
This is going to be a perpetual issue since we seem to almost always have broken links. The idea is this is a way to communicate that someone has done something to notify webmasters that their site is broken. For example, a day or two ago, I emailed fatcatlab to let them know their site was down and they were able to fix it.
The text was updated successfully, but these errors were encountered: