Skip to content

ecad: rename a part symbol file whose name Windows cannot check out (fixes Build and Package Main) - #130

Merged
finger563 merged 1 commit into
mainfrom
fix/ecad-windows-safe-symbol-path
Oct 13, 2026
Merged

finger563 merged 1 commit into
mainfrom
fix/ecad-windows-safe-symbol-path

Conversation

@finger563

Copy link
Copy Markdown
Contributor

"Build and Package Main" has failed on every push to main since the ecad update. The build job is fine; the package job fails on windows-latest before doing anything, because its action checks the repository out and the checkout refuses one path:

error: invalid path 'ecad/elec/src/parts/Ckmtw_B_2100S02P_A110/210S-1*2PL=11.6MMGold-platedblack.kicad_sym'
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128

* is not a legal filename character on Windows. This is the only tracked path containing one of * ? : " < > | \ (scanned the full tracked-file list).

Fix: rename the KiCad symbol file to 210S-1x2PL_11.6MMGold-platedblack.kicad_sym (also dropping =), rename the symbol units inside it to match, and update the symbol= reference in the part's is_atomic_part trait. The part's Value property keeps the manufacturer's original string.

Verified: ato build -b box-emu-base (the one target that uses this part) passes with the offline components stand-in — PCB update, BOM, pinout all succeed; the only reported error is the unrelated LCSC datasheet download returning HTML. The checked-in layout is untouched (the local build's serialization churn was reverted, per the ecad CI notes).

🤖 Generated with Claude Code

https://claude.ai/code/session_01AWhoGwibqcKDhcG17mjVT1

`ecad/elec/src/parts/Ckmtw_B_2100S02P_A110/210S-1*2PL=11.6MMGold-platedblack.kicad_sym`
contains `*`, which is not a legal path character on Windows. Every run of
"Build and Package Main" since the ecad update has failed in the package job:
its action checks the repository out on windows-latest, and git aborts with
`error: invalid path 'ecad/elec/src/parts/.../210S-1*2PL=...kicad_sym'`.

Rename it to `210S-1x2PL_11.6MMGold-platedblack.kicad_sym` (also dropping `=`)
and update the symbol names inside it and the `symbol=` reference in the
part's `.ato` trait. It is the only tracked path with a Windows-illegal
character. `ato build -b box-emu-base` (the one target that uses the part)
still passes with the offline components stand-in.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AWhoGwibqcKDhcG17mjVT1
Copilot AI balanced review requested due to automatic review settings October 13, 2026 14:44

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The filename, internal symbol identifiers, and consuming reference are consistent, with no stale references remaining.

0 open findings

What changed in this PR

Renames the KiCad symbol to a Windows-compatible filename, restoring package checkout on Windows.

Changes:

  • Replaces invalid * and = filename characters.
  • Updates internal symbol names and the atopile reference.
File Description
Ckmtw_B_2100S02P_A110.ato References the renamed symbol file.
210S-1x2PL_11.6MMGold-platedblack.kicad_sym Renames the symbol and its unit consistently.

🧠 Review effort: Balanced


💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@finger563

Copy link
Copy Markdown
Contributor Author

Proof before merge: dispatched "Build and Package Main" on this branch — https://github.com/esp-cpp/esp-box-emu/actions/runs/38415975471 — build ✓ and all three package jobs (windows-latest, macos-latest, ubuntu-latest) ✓. The same workflow has failed on every push to main since the ecad update.

@finger563
finger563 merged commit 66834cf into main Oct 13, 2026
6 checks passed
@finger563
finger563 deleted the fix/ecad-windows-safe-symbol-path branch October 13, 2026 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants