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/34504567283
> [!WARNING]
> **Code Push Failed**: A code push safe output failed, and subsequent safe outputs were cancelled.
**Code Push Errors:**
- `create_pull_request`: Cannot create pull request: patch modifies files outside the allowed-files list. Add the files to the allowed-files configuration field or remove them from the patch.
Show 1 blocked file
`dashboard/site/test/unit/ui-elements.test.js`
> [!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.
>
>
### 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/34504567283
````
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/34504567283`
> [!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/34504567283) · copilot · 311 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 17, 2026, 5:14 PM UTC
Contributor guide
Research direction
Start with .github/workflows/self-care-dashboard-performance.md and inspect the failed run linked in the issue. Review the cache-memory references and allowed-files configuration against the blocked dashboard/site/test/unit/ui-elements.test.js file. Done means the workflow finds the intended cached data and can create its pull request without modifying disallowed files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd, devops, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100