Fix markdown_link_check test failures due to GitHub API rate limiting · Issue #1621 · trailofbits/dylint · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The CI test markdown_link_check frequently fails with 429 (Too Many Requests) status codes when validating GitHub links. This happens because the test hits GitHub's rate limit for unauthenticated API requests, which is limited to 60 requests per hour.
Currently, the test only allows for empty lines and 500 status codes in its assertion, causing it to fail when encountering 429 errors. The test runs npx markdown-link-check on all markdown files in the repository, which creates numerous requests to GitHub API endpoints.
This issue affects both CI pipelines and local development, making it difficult to run the full test suite reliably.
Checklist:
Skip the test when a GitHub token isn't available.
Add GitHub token authentication to increase rate limits (from 60 to 5000 requests/hour)
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
The CI test
markdown_link_check
frequently fails with 429 (Too Many Requests) status codes when validating GitHub links. This happens because the test hits GitHub's rate limit for unauthenticated API requests, which is limited to 60 requests per hour.Currently, the test only allows for empty lines and 500 status codes in its assertion, causing it to fail when encountering 429 errors. The test runs
npx markdown-link-check
on all markdown files in the repository, which creates numerous requests to GitHub API endpoints.This issue affects both CI pipelines and local development, making it difficult to run the full test suite reliably.
Checklist:
Skip the test when a GitHub token isn't available.Add GitHub token authentication to increase rate limits (from 60 to 5000 requests/hour)The text was updated successfully, but these errors were encountered: