Conversation
Sphinx linkcheck fails CI because the NIST dataplot URL for Pearson's Contingency Coefficient returns 504 Gateway Timeout from CI network, matching the existing linkcheck_ignore pattern used for other unreachable-from-CI reference links. --- Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com>
Borda
added
bug / fix
bhimrazy
approved these changes
Jul 15, 2026
ethanwharris
approved these changes
Jul 16, 2026
Borda
enabled auto-merge (squash)
July 16, 2026 11:06
Collaborator
Author
|
@justusschock ^^ pls |
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
3 participants
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.
What does this PR do?
Sphinx linkcheck fails CI because the NIST dataplot URL for Pearson's Contingency Coefficient returns 504 Gateway Timeout from CI network, matching the existing linkcheck_ignore pattern used for other unreachable-from-CI reference links.
Before submitting
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃