`result.statusCode: 0` being returned by many external links

[chris-dura]

I've recently started getting a result.statusCode: 0 returned when checking my markdown files.

'use strict';

/**
 * @fileoverview This is a stub test to use the `markdown-link-check` library directly,
 * to test whether the problem is truly with `markdown-link-check`,
 * or the underlying `link-check` library
 */

const markdownLinkCheck = require('markdown-link-check');

markdownLinkCheck('[example](http://google.com)', function (err, results) {
	if (err) {
		console.error('Error', err);
		return;
	}
	results.forEach(function (result) {
		console.log('%s is %s', result.link, result.status, result.statusCode);
	});
});

markdownLinkCheck('[example](https://dequeuniversity.com/screenreaders/voiceover-keyboard-shortcuts)', function (err, results) {
	if (err) {
		console.error('Error', err);
		return;
	}
	results.forEach(function (result) {
		console.log('%s is %s', result.link, result.status, result.statusCode);
	});
});


// output:
// http://google.com is alive 200
// https://dequeuniversity.com/screenreaders/voiceover-keyboard-shortcuts is dead 0

Is this perhaps related to tcort/link-check#47 (comment)?

[mtojek]

Hey @tcort! Do you think that it would be feasible to introduce a generic retry parameter? In coder/coder we can observe some transient network issues which could be fixed with a simple retry/backoff mechanism.

[Zvikan]

We also observe similar issues with status code 0 for some links, a manual retry to our GH action usually fix it, would prefer to have the markdown link checker make that retry.

[codefromthecrypt]

https://developer.android.com/build/multidex#avoid as well

[github-actions]

This issue has been marked as stale because it has been open 60 days with no activity. It will be closed in 30 days unless the stale label is removed or someone adds a comment.

[not-not-kevin]

This issue is still occurring for me.