Link Checker Report
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- tex
- Domain
- documentation
Research direction
Start with the full GitHub Actions output and the reported generated files: _site/discrete_dp.html, _site/genindex.html, _site/prf-prf.html, and _site/search.html. Trace the three 404 links and the file:///None references back to their inputs, then regenerate the site and rerun the link checker. Done means the six reported errors are resolved and the checker reports no errors.
Written by the indexing model from the issue text.
Description
Summary
| Status | Count |
|---|---|
| 🔍 Total | 9082 |
| 🔗 Unique | 2220 |
| ✅ Successful | 9076 |
| ⏳ Timeouts | 0 |
| 🔀 Redirected | 44 |
| 👻 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
- Dominant language
- TeX
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from QuantEcon/lecture-dp
-
Link Checker ReportOpenautomated issue linkchecker report
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
QuantEcon/lecture-dp#68 ·
-
Link Checker ReportOpenautomated issue linkchecker report
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
QuantEcon/lecture-dp#67 ·
-
Link Checker ReportOpenautomated issue linkchecker report
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
QuantEcon/lecture-dp#65 ·
-
Link Checker ReportOpenautomated issue linkchecker report
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
QuantEcon/lecture-dp#62 ·
-
Link Checker ReportOpenautomated issue linkchecker report
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
QuantEcon/lecture-dp#59 ·
All issues in QuantEcon/lecture-dp
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
aws-samples/sample-per-model-bedrock#616 ·
Maintainers usually reply within 1 day
-
area:quality p3-medium ready-for-agent type:docs
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
fderuiter/deruiter.dev#3589 · 1 comment ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
intake mcp-intake needs-human-review priority:high type:bug
Difficulty 1/5 Under an hour Newbie friendliness 83/100
Ikalus1988/MisakaNet#4064 · 2 comments ·
Maintainers usually reply within 1 day
-
status:needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
PX4/PX4-Autopilot#29496 ·
Maintainers usually reply within 1 day