[aw] Repo Pulse — Daily Report reported incomplete result
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 991
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 196
Description
### Workflow Failure
**Workflow:** [Repo Pulse — Daily Report](https://github.com/microsoft/aspire/blob/main/.github/workflows/repo-pulse.md)
**Branch:** main
**Run:** https://github.com/microsoft/aspire/actions/runs/34374113416
> [!WARNING]
> **Task Could Not Be Completed**: The agent reported that the task could not be performed due to an infrastructure or tool failure.
**Reasons:**
- Accidental invalid update_issue call consumed the single allowed call
A first update_issue call was made using the CLI's --body - argument, intending to pipe body content from stdin, but the tool treated the literal string "-" as the body value instead of reading from stdin. This incorrectly replaced issue #16404's body with the literal text "-". The correct update_issue call with the full generated Repo Pulse report body (composed from .repo-pulse/*.json data files) was attempted immediately after but rejected with error E002: update_issue limit reached — 1 of 1 already used this run. The fully composed correct report body (16811 chars) was ready and saved at /tmp/gh-aw/agent/body.md covering all required sections (header, Notable Changes, Recently Merged PRs, Recently Opened PRs, Recently Filed Issues, PRs Awaiting Review, Activity Highlights) but could not be submitted due to the per-run call limit. Manual re-run of the workflow or an increased call limit is needed to apply the correct body to issue #16404.
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/microsoft/aspire/actions/runs/34374113416
````
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 repo-pulse failure in https://github.com/microsoft/aspire/actions/runs/34374113416`
> [!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 [Repo Pulse — Daily Report](https://github.com/microsoft/aspire/actions/runs/34374113416) · 94.4 AIC · [◷](https://github.com/search?q=repo%3Amicrosoft%2Faspire+is%3Aissue+%22gh-aw-workflow-id%3A+repo-pulse%22&type=issues)
> - [x] expires on Sep 16, 2026, 4:12 PM UTC
Contributor guide
Research direction
Start by reading .github/workflows/repo-pulse.md and the linked failed run. Then read .github/skills/agentic-workflows/SKILL.md or the referenced gh-aw debug guide and reproduce or inspect the report_incomplete failure. Done means identifying the workflow or tool-handling cause and confirming that a rerun can update the intended report issue without the invalid call or call-limit failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100