QuantEcon / QuantEcon/lecture-dp
Link Checker Report
Open
Nobody has claimed this yet.
automated
broken-links
report
- Dominant language
- TeX
- Stars
- 0
- Forks
- 0
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
Summary
| Status | Count |
|---|---|
| π Total | 9082 |
| π Unique | 2220 |
| β Successful | 9076 |
| β³ Timeouts | 0 |
| π Redirected | 46 |
| π» Excluded | 0 |
| β Unknown | 0 |
| π« Errors | 6 |
| β Unsupported | 0 |
Errors per input
Errors in _site/discrete_dp.html
- [404] https://python-intro.quantecon.org/optgrowth.html (at 949:47) | Rejected status code: 404 Not Found
- [404] https://python-intro.quantecon.org/optgrowth.html (at 956:77) | Rejected status code: 404 Not Found
- [404] https://python.quantecon.org/optgrowth.html#exercises (at 1397:64) | Rejected status code: 404 Not Found
Errors in _site/genindex.html
- [ERROR] file:///home/runner/work/lecture-dp/lecture-dp/_site/None (at 868:83) | File not found. Check if file exists and path is correct
Errors in _site/prf-prf.html
- [ERROR] file:///home/runner/work/lecture-dp/lecture-dp/_site/None (at 665:83) | File not found. Check if file exists and path is correct
Errors in _site/search.html
- [ERROR] file:///home/runner/work/lecture-dp/lecture-dp/_site/None (at 674:83) | File not found. Check if file exists and path is correct
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up β it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported errors in _site/discrete_dp.html, _site/genindex.html, _site/prf-prf.html, and _site/search.html, then trace each generated link back to its source. Check the linked GitHub Actions output for context. Done means the six reported errors are resolved and the link checker completes without these failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- tex
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100