Fix repo-memory patch size and cache-memory miss in daily workflows#35202
Merged
Conversation
- Fix #35105: Increase max-patch-size for Daily Community Attribution Updater from 10KB to 100KB so the full contributors list can be saved - Fix #35135: Add first-run guidance to Step Name Alignment prompt to prevent spurious cache_memory_miss failures on empty cache Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix CGO build failures causing CI confidence degradation
Fix repo-memory patch size and cache-memory miss in daily workflows
May 27, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Fixes two recurring daily-workflow failure issues by adjusting workflow frontmatter and an embedded prompt instruction, then recompiling the corresponding lock files.
Changes:
- Raise
repo-memory.max-patch-sizeto 102400 bytes (100KB) indaily-community-attribution.mdso the full contributors list can be pushed. - Add an explicit "first run / empty cache" instruction to
step-name-alignment.mdtelling the agent not to emitmissing_data: cache_memory_misson an empty cache. - Recompile both
.lock.ymlfiles to reflect the source changes (hashes,MAX_PATCH_SIZEenv,push_repo_memoryconfig, prompt heredoc tags).
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/daily-community-attribution.md | Adds max-patch-size: 102400 to the repo-memory config. |
| .github/workflows/daily-community-attribution.lock.yml | Recompiled lock; MAX_PATCH_SIZE and push_repo_memory.max_patch_size updated to 102400; regenerated heredoc tags and metadata hash. |
| .github/workflows/step-name-alignment.md | Adds first-run guidance to skip missing_data when no cache exists yet. |
| .github/workflows/step-name-alignment.lock.yml | Recompiled lock; updated body_hash to reflect the prompt change. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 4/4 changed files
- Comments generated: 0
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.
Two daily workflows were generating failure issues: the Community Attribution Updater was exceeding the default 10KB repo-memory patch limit, and Step Name Alignment was reporting spurious
cache_memory_missfailures on first run (empty cache).Daily Community Attribution Updater —
max-patch-size(#35105)The full contributors list exceeds the 10KB default. Raised
max-patch-sizeto 100KB (the allowed maximum):This propagates into the compiled lock file's
MAX_PATCH_SIZEenv var and thepush_repo_memorysafe-outputs handler config.Step Name Alignment — cache-memory miss (#35135)
The system-level
cache_memory_prompt.mdinstructs agents to callmissing_datawithreason: cache_memory_misswhenever no cached data is found. On first run the cache is legitimately empty, buthandle_agent_failure.cjstreats anycache_memory_misssignal as a misconfiguration and creates a failure issue.Added an explicit override in the prompt:
Both
.lock.ymlfiles recompiled after the frontmatter/body changes.