novox/mesh-catalog
9
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

mesh-build-go reaches the forge's git when the public proxy is unreachable, and a network failure is no pin (issue 1966) #647

Merged
mesh-tools merged 2 commits from fix/1966-contracts-goproxy into main 2026-11-09 22:08:33 +00:00
Conversation 1 Commits 2 Files Changed 4
+16 -3
2 Commits
Author SHA1 Message Date
jschoubben 407fc6c9e6 The Go seat goes on to the public proxy only on a 404, the public proxy to direct on any failure (issue 1966, review 1)
mesh/delivery merged: source.main moved to novox/mesh-catalog@8b184d83222c
Details
mesh/check checking 407fc6c9e625 on 9c42423d5821 
Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
 2026-11-09 22:55:53 +01:00
jschoubben 6299b47f4f A mesh package the Go seat lacks is fetched from the forge's git, not stopped by an unreachable public proxy (issue 1966) 
GOPROXY joined the Go seat, the public proxy and direct with commas, so go went on only after a 404 or 410: a contracts
package the seat does not hold, and a public proxy a node cannot reach, ended the fetch before direct. It joins them
with | now, so any failure goes on to the next. go words a proxy it cannot reach as "invalid version", which the pin
path read as an unknown revision and labelled "on no pull request head"; a network failure is never that now
(network is unreachable and no route to host are network failures).

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
 2026-11-09 22:42:09 +01:00