Skip to content

Broken Links Found in Documentation #546

Closed as not planned
Closed as not planned

Description

@github-actions

Link Check Report

🚨 2 broken link(s) and 0 redirect(s) were found in the documentation.

Details:

  • Repository: QuantEcon/lecture-python-programming
  • Workflow: Link Checker [Anaconda, Linux]
  • Run ID: 25348771300
  • Commit: 1b356ab
  • Branch: main
  • Date: 2026-05-04T23:25:06.958Z

Link Check Summary

  • Total broken links: 2
  • Total redirects found: 0

Broken Links

_site/pandas.html - 2 broken link(s):
❌ https://fred.stlouisfed.org/ - Status: 0 (Timeout)
Link text: FRED
❌ https://fred.stlouisfed.org/series/UNRATE - Status: 0 (Timeout)
Link text: unemployment rate


Next Steps:

  1. Review the broken links listed above
  2. Update or remove broken links from the source files
  3. Consider applying AI suggestions for better alternatives
  4. Re-run the link check to verify fixes

Note: This issue was automatically created by the AI-Powered Link Checker Action.

Please close this issue once all broken links have been addressed.

Activity

  1. added
    bugSomething is wrong or broken in a lecture or build
    documentationRepo docs and contributor meta (not lecture content)
    broken-linksLink checker found dead links
    on May 4, 2026
  2. mmcky commented on Aug 3, 2026

    @mmcky
    Contributor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    broken-linksLink checker found dead linksbugSomething is wrong or broken in a lecture or builddocumentationRepo docs and contributor meta (not lecture content)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions