fix: move default wazero cache outside mcp-logs artifact path#5698
Merged
Conversation
Copilot
AI
changed the title
[WIP] Fix move wazero cache outside mcp-logs to prevent artifact upload EACCES failures
fix: move default wazero cache outside mcp-logs artifact path
May 14, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Relocates the default wazero compilation cache from inside <log-dir> to a sibling directory, avoiding inclusion in the mcp-logs artifact glob (which was causing EACCES zip failures due to restrictive cache file perms).
Changes:
defaultWasmCacheDirnow returnsfilepath.Dir(logDir)/wazero-cache(sibling), with an empty-logDir fallback to the bare name.- Updated
--wasm-cache-dirhelp text in both root logging flags andproxycommand. - Updated tests and comments to reflect sibling-path semantics.
Show a summary per file
| File | Description |
|---|---|
| internal/cmd/wasm_cache.go | Compute cache dir as sibling of logDir; handle empty logDir. |
| internal/cmd/proxy.go | Help text updated to describe sibling default. |
| internal/cmd/proxy_test.go | Comment/message updated to reflect sibling behavior. |
| internal/cmd/flags_logging.go | Help text updated to describe sibling default. |
| internal/cmd/flags_logging_test.go | Test expectation updated to sibling path; wording adjusted. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 5/5 changed files
- Comments generated: 0
This was referenced May 14, 2026
This was referenced May 14, 2026
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
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.
The wazero compilation cache was defaulting under
mcp-logs, and cache files created with restrictive permissions caused artifact zipping to fail (EACCES), which then cascaded into downstream detection failures due to missing agent artifacts. This change relocates the default cache path to avoid inclusion in themcp-logsartifact glob.Cache path resolution
defaultWasmCacheDir(logDir)to placewazero-cacheas a sibling oflogDirinstead of a child directory./tmp/gh-aw/mcp-logs/wazero-cacheto/tmp/gh-aw/wazero-cache.CLI/help text alignment
--wasm-cache-dirhelp text in both root logging flags and proxy command to reflect the new default semantics.Behavioral test updates
Post-release risk check
mcp-logswith restrictive permissions; no additional cases were identified.