-
Notifications
You must be signed in to change notification settings - Fork 120
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
Started failing for valid link containing %28/%29 after release of [email protected] #142
Comments
Downgrading to |
pi@pi:~/m-l-c $ cat issue.md
# Issue
[link](https://en.wikipedia.org/wiki/Glob_%28programming%29)
pi@pi:~/m-l-c $ npm install [email protected] --no-package-lock
+ [email protected]
pi@pi:~/m-l-c $ npm install [email protected] --no-package-lock
+ [email protected]
pi@pi:~/m-l-c $ ./node_modules/.bin/markdown-link-check --verbose issue.md
FILE: issue.md
[✓] https://en.wikipedia.org/wiki/Glob_%28programming%29 → Status: 200
1 links checked.
pi@pi:~/m-l-c $ |
I reproduced and confirmed the bug. I will investigate on the link-check side first. |
Also fails on this link: |
For those who uses |
I've encountered numerous failures in the last 2 days since the latest was pushed. As noted above all occurrences have URLEncoded elements.
|
I've published version 3.8.5 which should solve this. |
@tcort thanks, but it doesn't seem working: gaurav-nelson/github-action-markdown-link-check#86 |
$someone has fixed my example link |
It looks like gaurav-nelson/github-action-markdown-link-check#86 tests are successful. The correct Polkadot link is https://research.web3.foundation/en/latest/polkadot/economics/1-token-economics.html#inflation-model, the one you provided is broken and is reported as broken by link-check not because of the % but because the page doesn't exist (deleted?) and was not redirected, that seems correct to me. |
yes, the link was as I mentioned yesterday. Now I'll put |
Thanks, I've only been able to re-tests one occurrence but it does seem fixed. |
This worked 24 hours ago (I run CI nightly) with v3.8.3 and fails now with v3.8.4. However, downgrading to v3.8.3 does not help. Perhaps a dependency updated their patch version?
The text was updated successfully, but these errors were encountered: