[GH-ISSUE #1532] fix(ci): codespell flags valid technical terms -- add .codespellrc ignore list #13535

Closed
opened 2026-05-17 17:41:18 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @Shashank-Tripathi-07 on GitHub (Apr 25, 2026).
Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/1532

Problem

The Check for spelling errors CI check has been failing on every PR because codespell has no ignore list configured. It flags legitimate technical terms used throughout the codebase as misspellings:

Flagged word Actual meaning Location
Clos Clos network topology (standard datacenter term) slides/vol2/03_network_fabrics/
FPR False Positive Rate (ML metrics term) slides/vol1/15_responsible_engr/, slides/vol2/16_responsible_ai/
Rin Variable name for ring buffer / ring allreduce README.md
Curren Contributor name "Curren Iyer" README.md
finalY jsPDF Y-coordinate variable socratiq/src_shadow/js/
foundIn camelCase variable name socratiq/src_shadow/js/
ans Short variable name socratiq/src_shadow/js/
extit LaTeX \textit truncated in source slides/
targetin camelCase variable socratiq/src_shadow/js/

Fix

Add a .codespellrc at the repo root:

[codespell]
skip = ./.git,./node_modules,./socratiq/src_shadow
ignore-words-list = clos,fpr,rin,ans,fo

The socratiq/src_shadow/ directory contains vendored/compiled JS and should be skipped entirely. The remaining false positives (Clos, FPR, Rin, ans) are genuine domain terms that should be whitelisted.

Impact

This check has been failing on every merged PR (e.g. #1527, #1526, #1525) without blocking merges, meaning it provides no signal. Adding the ignore list will make the check meaningful again.

Originally created by @Shashank-Tripathi-07 on GitHub (Apr 25, 2026). Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/1532 ## Problem The `Check for spelling errors` CI check has been failing on every PR because `codespell` has no ignore list configured. It flags legitimate technical terms used throughout the codebase as misspellings: | Flagged word | Actual meaning | Location | |---|---|---| | `Clos` | Clos network topology (standard datacenter term) | `slides/vol2/03_network_fabrics/` | | `FPR` | False Positive Rate (ML metrics term) | `slides/vol1/15_responsible_engr/`, `slides/vol2/16_responsible_ai/` | | `Rin` | Variable name for ring buffer / ring allreduce | `README.md` | | `Curren` | Contributor name "Curren Iyer" | `README.md` | | `finalY` | jsPDF Y-coordinate variable | `socratiq/src_shadow/js/` | | `foundIn` | camelCase variable name | `socratiq/src_shadow/js/` | | `ans` | Short variable name | `socratiq/src_shadow/js/` | | `extit` | LaTeX `\textit` truncated in source | `slides/` | | `targetin` | camelCase variable | `socratiq/src_shadow/js/` | ## Fix Add a `.codespellrc` at the repo root: ```ini [codespell] skip = ./.git,./node_modules,./socratiq/src_shadow ignore-words-list = clos,fpr,rin,ans,fo ``` The `socratiq/src_shadow/` directory contains vendored/compiled JS and should be skipped entirely. The remaining false positives (`Clos`, `FPR`, `Rin`, `ans`) are genuine domain terms that should be whitelisted. ## Impact This check has been failing on every merged PR (e.g. #1527, #1526, #1525) without blocking merges, meaning it provides no signal. Adding the ignore list will make the check meaningful again.
GiteaMirror added the javascripttype: bugarea: socratiq labels 2026-05-17 17:41:19 -05:00
Author
Owner

@profvjreddi commented on GitHub (Apr 25, 2026):

Awesome, thanks @Shashank-Tripathi-07 - yea definitely need to fix it. I was going to make a full sweeping pass on it later today.

<!-- gh-comment-id:4319652977 --> @profvjreddi commented on GitHub (Apr 25, 2026): Awesome, thanks @Shashank-Tripathi-07 - yea definitely need to fix it. I was going to make a full sweeping pass on it later today.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/cs249r_book#13535