Closed DavidAnson closed 3 years ago
Downgrading to link-check@4.5.2
fixes the break.
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 markdown-link-check@3.8.3 --no-package-lock
+ markdown-link-check@3.8.3
pi@pi:~/m-l-c $ npm install link-check@4.5.2 --no-package-lock
+ link-check@4.5.2
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: https://research.web3.foundation/en/latest/polkadot/Token%20Economics.html#inflation-model
For those who uses markdown-link-check
within gaurav-nelson/github-action-markdown-link-check/
Github Action I've had an issue with %20
in URL and had to workaround it with https://github.com/gaurav-nelson/github-action-markdown-link-check/issues/85
I've encountered numerous failures in the last 2 days since the latest was pushed. As noted above all occurrences have URLEncoded elements. Ex:
I've published version 3.8.5 which should solve this.
@tcort thanks, but it doesn't seem working: https://github.com/gaurav-nelson/github-action-markdown-link-check/pull/86
$someone has fixed my example link https://research.web3.foundation/en/latest/polkadot/Token%20Economics.html#inflation-model
and now I fail to find a good example with %20
It looks like https://github.com/gaurav-nelson/github-action-markdown-link-check/pull/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 https://www.google.com/?q=url%20with%20a%20space
to a test. And yes, it's working.
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?