-
Notifications
You must be signed in to change notification settings - Fork 88
Description
In #642, the linkinator
CLI was reportedly hanging after scanning a large site. I'm running into a similar issue on my personal site: ammrat13/ammrat13.github.io@821a743. The site isn't that large - just 109 links that scan in two seconds. On my local machine, linkinator
spends several minutes after the final "Successfully scanned" message before exiting. On GitHub Actions, JustinBeckwith/linkinator-action@v1
does not terminate even after 20 minutes. This behavior is not present when the scan fails - in that case, linkinator
exits immediately.
To reproduce, you can try building the site from the repository. Alternatively, I've attached the generated HTML and the linkinator.config.json
. I run:
$ # Assume: site.tar.xz and linkinator.config.json are in the current directory
$ tar -xvf site.tar.xz
$ npm install linkinator
$ npx linkinator ./_site/
This may give spurious 429
errors. I solved this by reducing the --concurrency
.