-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
workflows: Allow urls-check to write issues #20166
Conversation
Commit bc7e2bf was wrong: This workflow only doesn't need any permissions if all URLs are valid. But if not, then it wants to update/create an issue to notify us about that.
The manual run against this branch, and it passed again. It filed #20167 |
This might tell us what's wrong about that dmtf.org URL when running in GitHub (issue #20167).
#20167 is bogus. I added another commit here to get some more data, and triggered another run |
OK, that must have been a transient network issue then .. the last check was ok, see #20168. To test the second commit, I deliberately damaged that URL in the source (
|
failed.append(url) | ||
except urllib.error.URLError: | ||
failed.append(url) | ||
failed.append(f"{url} : {resp.getcode()} {resp.reason}") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As this looks a bit unusual/asymmetric, I tested this code path as well, by changing the 400 to 200, and then got:
Checked 177 URLs out of which 1 is/are invalid:
https://www.dmtf.org/sites/default/files/standards/documents/DSP0134_2.7.1.pdf: 200 OK
Commit bc7e2bf was wrong: This workflow only doesn't need any permissions if all URLs are valid. But if not, then it wants to update/create an issue to notify us about that.
Fixes this failure which started to happen 3 weeks ago.