Add retry and timeout configuration to link checker#6
Merged
Conversation
- Add --max-retries 3 to retry failed links up to 3 times - Add --timeout 30 to increase timeout from default to 30 seconds - This should handle temporary failures and slow responses from open-std.org Co-authored-by: pgit <1456612+pgit@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix timeouts in link checker report
Add retry and timeout configuration to link checker
Feb 4, 2026
Copilot stopped work on behalf of
pgit due to an error
February 4, 2026 20:44
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Link checker was experiencing transient timeouts on
open-std.orgPDF links. Configure lychee with retry logic and extended timeout to handle flaky upstream servers.Changes
--max-retries 3flag to retry failed links before marking as timeout--timeout 30flag (increased from default 20s) for slow-responding serversEliminates false positives from temporary network issues without requiring manual workflow re-runs.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.