githubnext / githubnext/gh-aw-cao
[aw] SelfCare / Dashboard Performance has cache-memory miss misconfiguration
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 1
- Avg merge
- 49m
- Merged PRs (30d)
- 837
Description
### Workflow Failure
**Workflow:** [SelfCare / Dashboard Performance](https://github.com/githubnext/gh-aw-cao/blob/main/.github/workflows/self-care-dashboard-performance.md)
**Branch:** main
**Run:** https://github.com/githubnext/gh-aw-cao/actions/runs/34407421633
> [!WARNING]
>
> Cache Configuration Problem: cache miss detected after cache restore succeeded.
>
> The agent reported a cache miss (`missing_data` with `reason: cache_memory_miss`) after the workflow successfully restored cache-memory for this run. This likely indicates the prompt is misconfigured and the agent cannot locate the correct file path within the cache directory.
>
> This warning is shown only when a cache restore matched an existing key. Cache misses can be expected on first runs and on branches where `actions/cache` has no visible entries due to branch scoping.
>
> Review the [cache-memory configuration](https://github.github.com/gh-aw/reference/cache-memory/) and ensure the agent prompt correctly references files inside the cache directory.
>
> **File naming convention:** Cache files are stored at `/tmp/gh-aw/cache-memory/` (default) or `/tmp/gh-aw/cache-memory-{id}/` for additional caches. Use descriptive file and directory names with subdirectories for organization.
>
>
> [!WARNING]
> **Task Could Not Be Completed**: The agent reported that the task could not be performed due to an infrastructure or tool failure.
**Reasons:**
- artifact_upload_failed
upload_artifact rejected the evidence path twice. Attempt 1 used a symlink at /tmp/gh-aw/agent/self-care-dashboard-performance-34407421633 and failed with: symlinks are not allowed. Attempt 2 copied the evidence tree to /tmp/gh-aw/agent/self-care-dashboard-performance-34407421633 and failed with: path is outside allowed source roots (GITHUB_WORKSPACE, staging directory).
This is a structured incompletion signal (`report_incomplete`), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.
### Action Required
**Assign this issue to an agent** to debug and fix the issue.
Debug with any coding agent
Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):
````
Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md
The failed workflow run is at https://github.com/githubnext/gh-aw-cao/actions/runs/34407421633
````
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the `agentic-workflows` prompt.
- Start your agent
- Load the `agentic-workflows` skill from `.github/skills/agentic-workflows/SKILL.md` or
- Type `debug the agentic workflow self-care-dashboard-performance failure in https://github.com/githubnext/gh-aw-cao/actions/runs/34407421633`
> [!TIP]
>
> Stop reporting this workflow as a failure
>
> To stop a workflow from creating failure issues, set `report-failure-as-issue: false` in its frontmatter:
> ```yaml
> safe-outputs:
> report-failure-as-issue: false
> ```
>
>
> Generated from [SelfCare / Dashboard Performance](https://github.com/githubnext/gh-aw-cao/actions/runs/34407421633) · copilot · 219.2 AIC · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-cao+is%3Aissue+%22gh-aw-workflow-id%3A+self-care-dashboard-performance%22&type=issues)
> - [x] expires on Sep 16, 2026, 9:47 PM UTC
Contributor guide
Research direction
Start with .github/workflows/self-care-dashboard-performance.md, the failed run, and debug.md. Review the cache-memory configuration reference and the agent prompt paths, then investigate the artifact_upload_failed evidence path reported by the run. Done means the workflow locates restored cache files and uploads evidence successfully on a rerun.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100