fix(smoke): --noproxy for local download + surface curl errors (arm64 12a)#905
Merged
Conversation
… 12a) Phase 12a swallowed curl's stderr (2>/dev/null), so the persistent windows-arm64 "curl download failed" was undiagnosable. Two changes: (1) add --noproxy '*' so curl never routes the local 127.0.0.1 test server through a proxy env var -- a strong candidate since the app's own WinHTTP downloader reaches the server in Phase 14 while only msys2 curl fails, instantly; (2) print curl's stderr on failure so the actual reason is visible if it persists. Harmless on all platforms (the smoke server is always local). Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>
kapoorsunny
pushed a commit
to kapoorsunny/codebase-memory-mcp
that referenced
this pull request
Jul 6, 2026
The persistent windows-11-arm smoke Phase 12a failure was a 404, not a network error: it requested codebase-memory-mcp-windows-amd64.zip on the arm64 leg. Cause: DL_ARCH came from `uname -m`, which on windows-11-arm is an emulated x86_64 MSYS2 uname reporting "x86_64" -> wrong (amd64) archive -> 404 (server has arm64). Phase 14 worked because the binary's own detect_arch() is native. Prefer SMOKE_ARCH (passed from the smoke workflow's matrix.arch) over uname; fall back to uname for local runs. This is the real cause the earlier curl/proxy/ipv4 attempts masked -- the 404 was swallowed by 2>/dev/null until DeusData#905 surfaced it. Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Phase 12a swallowed curl's stderr (2>/dev/null), so the persistent windows-arm64
"curl download failed" was undiagnosable. Two changes: (1) add --noproxy '*' so
curl never routes the local 127.0.0.1 test server through a proxy env var -- a
strong candidate since the app's own WinHTTP downloader reaches the server in
Phase 14 while only msys2 curl fails, instantly; (2) print curl's stderr on
failure so the actual reason is visible if it persists. Harmless on all
platforms (the smoke server is always local).