[BUG]: Documentation and tutorial fixes: broken reference link in cuda-cpp contributing guide and typo in Ozaki-I notebook
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- cpp, jupyter-notebook
- Domain
- documentation
Research direction
Start in tutorials/cuda-cpp/CONTRIBUTING.md: fix the relative link on line 325 so it points to notebooks/01.02-Execution-Spaces/Solutions/no-magic-execution-space-changes.cpp, and correct "starts" to "start" on line 14. Then open tutorials/floating-point-emulation/notebooks/03-Ozaki-I-Emulation/03.01-UnfusedEmulation.ipynb, change "refering" to "referring" in markdown cell 1, and check that the link resolves. Done when both files are corrected and the link no longer 404s.
Written by the indexing model from the issue text.
Description
Is this a duplicate?
- I confirmed there appear to be no duplicate issues for this bug and that I agree to the Code of Conduct
Describe the bug
- In
tutorials/cuda-cpp/CONTRIBUTING.mdline 325, the link[here](Solutions/no-magic-execution-space-changes.cpp)points to a non-existent relative path. The actual solution file is located atnotebooks/01.02-Execution-Spaces/Solutions/no-magic-execution-space-changes.cpp. Additionally, line 14 has a subject-verb agreement mismatch (Traditional CUDA courses typically starts with...instead ofstart with). - In
tutorials/floating-point-emulation/notebooks/03-Ozaki-I-Emulation/03.01-UnfusedEmulation.ipynbmarkdown cell 1, "referring" is misspelled as "refering".
Steps to reproduce
- Navigate to
tutorials/cuda-cpp/CONTRIBUTING.mdand click the link on line 325 ([here](Solutions/no-magic-execution-space-changes.cpp)). It returns a 404 / file not found error. - Open
tutorials/floating-point-emulation/notebooks/03-Ozaki-I-Emulation/03.01-UnfusedEmulation.ipynband view markdown cell 1.
Expected behavior
- The link in
tutorials/cuda-cpp/CONTRIBUTING.mdshould resolve directly tonotebooks/01.02-Execution-Spaces/Solutions/no-magic-execution-space-changes.cpp. - Typos and grammar errors should be corrected.
Actual behavior
- The link leads to a missing target (
tutorials/cuda-cpp/Solutions/no-magic-execution-space-changes.cpp). - "refering" is used instead of "referring", and "courses ... starts" instead of "courses ... start".
Environment
All platforms (Documentation / Jupyter Notebook)
Additional context
I have a patch ready and will submit a PR linking to this issue.
- Dominant language
- Jupyter Notebook
- Stars
- 2.1k
- Forks
- 358
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 9
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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 NVIDIA/accelerated-computing-hub
-
Remove obsolete port-binding rewrite from brev/dev-start.bashPossibly taken @MaxFreedomPollard claimed this 42 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NVIDIA/accelerated-computing-hub#216 ·
Maintainers usually reply within 4 days
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
NVIDIA/accelerated-computing-hub#184 · 10 comments ·
Maintainers usually reply within 4 days
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
NVIDIA/accelerated-computing-hub#171 ·
Maintainers usually reply within 4 days
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
NVIDIA/accelerated-computing-hub#89 · 1 comment ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
NVIDIA/accelerated-computing-hub#85 ·
Maintainers usually reply within 4 days
All issues in NVIDIA/accelerated-computing-hub
Similar issues
-
LicenseOpen
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 85/100
ysb3996-blip/oops#51 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 25 days
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day