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
Closing as a duplicate of #587, which carries the same two FRED findings.
Both FRED URLs are false positives: they return 200 in well under a second from a normal network, and the 0 (Timeout) status is FRED throttling GitHub Actions runner IPs. They are already whitelisted for Sphinx in lectures/_config.yml under linkcheck_ignore, but the link checker scans built HTML and never sees that configuration, so it re-reports them every week.
The fix belongs in the action rather than in this repo. Tracked upstream in QuantEcon/action-link-checker#2, which requests an ignore-patterns input plus deduplication so a recurring finding updates one issue instead of opening a new one each week.
This report belongs to an older batch (2026-04-06 through 2026-05-25) that is missing from GitHub's issue search index, so it never appeared in the repository's open-issues list. That is why it is being closed a few months after the 2026-06 to 2026-07 batch rather than alongside it.
Activity
mmcky commentedon Aug 3, 2026
Closing as a duplicate of #587, which carries the same two FRED findings.
Both FRED URLs are false positives: they return
200in well under a second from a normal network, and the0 (Timeout)status is FRED throttling GitHub Actions runner IPs. They are already whitelisted for Sphinx inlectures/_config.ymlunderlinkcheck_ignore, but the link checker scans built HTML and never sees that configuration, so it re-reports them every week.The fix belongs in the action rather than in this repo. Tracked upstream in QuantEcon/action-link-checker#2, which requests an
ignore-patternsinput plus deduplication so a recurring finding updates one issue instead of opening a new one each week.This report belongs to an older batch (2026-04-06 through 2026-05-25) that is missing from GitHub's issue search index, so it never appeared in the repository's open-issues list. That is why it is being closed a few months after the 2026-06 to 2026-07 batch rather than alongside it.