-
Notifications
You must be signed in to change notification settings - Fork 17
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
Incorrect "the following links could not be resolved" list #28
Comments
Thanks for reporting. I will look into it. Do you use it in a public repo and can I see the failing/wrong checks? |
My mistake: I was sure, that I included the links to the logs! Sorry for that. Here is the output from CI with the |
By the way, https://deps.rs/repo/github/stanislav-tkach/os_info link is reported as "404 - Not Found", though the link is OK. |
I could reproduce this locally. The problem is that the link returns 404 on a HEAD request:
This is not an expected behavoir... though I might try a bit harder here and send another GET request which would give me a 200 then. I started with HEAD requests because they are so much cheaper... but yea, seems like there is a lot of unusual stuff out there...
This one is harder. I could not reproduce it locally, yet. :( I will try to find a solution as soon as I know how to debug this.... |
This is now fixed with release v0.14.0. |
Thanks! |
can be closed? |
Describe the bug
In some cases the resulting "the following links could not be resolved" list includes valid links. For example:
There are only three failures in the log above, but the list includes four links.
To Reproduce
Unfortunately I'm unable to create a minimal reproducible example, moreover this issue isn't reproduced locally. However, it is stably reproduced on CI. Perhaps the MLC github action can affect this somehow?
Here are logs with and without debug output.
Expected behavior
I expect to see no "[ OK ]" links in the "the following links could not be resolved" section.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: