microsoft / microsoft/aspire

[aw] Repo Pulse — Daily Report reported incomplete result

Open
#19,808 0 comments 0 reactions 0 assignees View on GitHub
agentic-workflows
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/33321263396

> [!WARNING]
> **Task Could Not Be Completed**: The agent reported that the task could not be performed due to an infrastructure or tool failure.

**Reasons:**
- An earlier accidental update_issue call (55 bytes, near-empty body) consumed the single allowed update_issue invocation for this run before the full Repo Pulse report body could be submitted. The safe-output quota (1 of 1) was exhausted, so the complete regenerated report could not be delivered to issue #16404 in this run.

Root cause: a stdin-redirection test (`cat body.md | safeoutputs update_issue --issue_number 16404 --operation replace --body -`) did not correctly pipe file content into the --body flag, resulting in a nearly empty body being submitted as the first (and only allowed) update_issue call. The properly assembled full report (all required sections: header, data quality banner, Notable Changes, Recently Merged PRs, Recently Opened PRs, Recently Filed Issues, PRs Awaiting Review, Activity Highlights) was built afterward in /tmp/gh-aw/agent/payload.json but rejected with E002 (update_issue limit reached, 1 of 1 already used this run). No other GitHub write actions were taken.

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/33321263396
````

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/33321263396`

> [!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/33321263396) · 118.7 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 6, 2026, 4:08 PM UTC

Contributor guide

Open the contributing guide

Research direction

Start with .github/workflows/repo-pulse.md and the failed run linked in the issue, then read .github/skills/agentic-workflows/SKILL.md and the referenced gh-aw debug guide. Trace the report_incomplete failure around the update_issue safe-output call and confirm the workflow can complete its report without this failure signal.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.