Prevent Agent Performance Analyzer repo-memory push failures by raising patch-size cap - #48012
Merged
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix repo-memory pruning path for push_repo_memory
Prevent Agent Performance Analyzer repo-memory push failures by raising patch-size cap
Jul 25, 2026
pelikhan
approved these changes
Jul 25, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Raises the Agent Performance Analyzer’s repo-memory budget to prevent expected memory writes from failing.
Changes:
- Increases
max-patch-sizefrom 10KB to 50KB. - Regenerates the compiled workflow with the updated constraint.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/agent-performance-analyzer.md |
Configures the 50KB repo-memory limit. |
.github/workflows/agent-performance-analyzer.lock.yml |
Applies the limit throughout generated runtime configuration. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 0
- Review effort level: Medium
Contributor
|
🎉 This pull request is included in a new release. Release: |
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.
Agent Performance Analyzer - Meta-Orchestratorwas treating a recoverable repo-memory size condition as a run failure path:push_repo_memoryrejected the write at the 10KB cap, then the agent stalled and was watchdog-terminated. This change removes that failure trigger by aligning the workflow’s repo-memory patch budget with observed memory shape.Root cause addressed
repo-memory.max-patch-size(10KB) while writing shared meta-orchestrator memory (metrics+*-latest.md), which routinely exceeds that limit.Workflow config update
.github/workflows/agent-performance-analyzer.md.github/workflows/agent-performance-analyzer.lock.ymlBehavioral impact
push_repo_memorynow has sufficient budget (50KB) for expected writes, avoiding the size-rejection → idle-loop → watchdog SIGTERM path for this workflow.