Test Templates matrix goes red on transient Go checksum DB and npm registry errors
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 36.3k
- Forks
- 1.9k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 33
Description
Description
CI infrastructure rather than a runtime bug, so the wails3 version / wails doctor fields don't apply. Affects .github/workflows/build-and-test-v3.yml on master.
Test Templates is a 3 OS x 8 template matrix. Each leg scaffolds a new module with wails3 init, which writes a fresh go.sum (so every dependency is verified against sum.golang.org) and a fresh node_modules. One failed request reds the leg, and the run reports failure on PRs that touched nothing related.
Two hits on 2026-08-26.
github.com/go-json-experiment/json@v0.0.0-20251027170946-4849db3c2f7e: verifying module: reading
https://sum.golang.org/tile/8/0/x178/138: stream error: stream ID 41; INTERNAL_ERROR; received from peer
Error: Cannot find native binding. npm has a bug related to optional dependencies
(https://github.com/npm/cli/issues/4828).
Why warming the module cache won't fix it
go-json-experiment/json is already in v3/go.sum, and task install builds the v3 CLI earlier in the same job, so the zip is already in GOMODCACHE. The tile fetch is driven by the template writing a new go.sum from scratch, not by the module download. Building v3 verifies against its existing go.sum and never consults the checksum DB, so the tile cache stays cold.
Expected behaviour
Transient network errors shouldn't fail the check. Genuine template breakage still should.
Out of scope
The same job also failed on apt-get getting a 403 from packages.microsoft.com (ubuntu-latest, react). Different step, noting it so it isn't conflated.
PR to follow.
Contributor 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.
Research direction
Start with .github/workflows/build-and-test-v3.yml and inspect the Test Templates matrix, including the wails3 init and dependency-install steps. Reproduce the checksum DB or npm registry failures, then verify that transient network errors no longer fail the check while genuine template breakage still does.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, nodejs
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100