Repository navigation
🐛🧑💻 - bugfix oversized progress evidence is reported as a retryable provider outage #547
Description
Is there an existing issue for this?
- I have searched the existing issues.
Which actions are affected?
Commits, Pull Request
Which platforms are affected?
Linux (observed; the policy is platform-independent)
Description
Dogfooding #538 / PR #546 found that a complete, valid large comparison is classified as a temporary provider outage. ProgressDiffRepository preserves its 256,000-byte evidence bound but throws provider.unavailable, with Retryable: Yes. The commit check fails although another identical attempt cannot fit the same deterministic input. Progress is correctly left unchanged and no model review is claimed.
Expected: preserve the bounded/completeness invariant, distinguish oversized evidence from an actual transient provider failure, and provide an actionable operator path. Any future bounded multi-part analysis needs an explicit contract and must not certify completion from truncated or partially reviewed changes. Do not raise the global limit, omit checks, truncate silently or claim this comparison was assessed as a workaround.
Reproducing the issue
- Inspect PR [#538] ✨ - feat reuse organization configuration and set up selected repositories in one guided session #546 at head
e6622daa33d345de8fba0853f0feef5aa2b1401fagainst baseb6d9910fb7b2d6888c711bacd52b3fc75e7e26dc. - Call GitHub compare with exact SHAs,
per_page=1&page=1, as the repository adapter does. - Validate all 148 comparison files and retain generated bundle/catalog metadata without their patches. No non-generated patch is missing.
- Serialize the evidence: 658,336 UTF-8 bytes, exceeding
MAX_EVIDENCE_BYTES = 256_000insrc/data/repository/progress_diff_repository.ts. - Observe Copilot - Commit run: no progress model request is made; persisted progress is retained, but the workflow fails as a retryable temporary outage.
Useful regression boundaries include the exact byte limit, the 299/300-file completeness boundary, missing patches, generated-metadata handling, SHA freshness, and a real transient provider failure. Error/recovery UX must preserve the distinction between unassessed progress and verified completion.
copilot Version
v3.5.6; reproduced while dogfooding PR #546 (the progress-diff policy is unchanged by that PR).
Relevant Log Output
A complete bounded branch comparison is unavailable. Progress was not assessed and existing state was retained.
Impact: The provider was temporarily unavailable.
Error code: provider.unavailable
Action: Retry when the provider is available.
Retryable: Yes
Additional context and comments
This is separate from the SDD schema failure fixed and published in v3.5.6, and separate from dependency vulnerability remediation. The mandatory check on develop for PR #546 is CI Check; this commit-analysis check is not mandatory. No branch-protection settings, evidence limits, labels or deployment gates were changed to bypass it.
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
vypbot commentedon Oct 17, 2026
Hi! I’m @vypbot, the Copilot assistant for this repository.
I can answer questions, explain the codebase, propose implementation and test plans, review issues and pull requests for potential bugs or security problems, and help authorized maintainers apply changes.
Try
/copilot helpto see the available commands, or mention @vypbot with your question.[-]🐛 - bugfix oversized progress evidence is reported as a retryable provider outage[/-][+]🐛🧑💻 - bugfix oversized progress evidence is reported as a retryable provider outage[/+]vypbot commentedon Oct 17, 2026
Implementation plan
Acceptance: A complete comparison at or below 256,000 serialized UTF-8 bytes remains eligible for review; one above the limit returns a distinct nonretryable error with actionable guidance, makes no model request, and retains existing progress, while transient provider failures remain retryable provider.unavailable errors.
Need something else? Mention the bot with a question or use
/copilot help.bugfix-547-bugfix-oversized-progress-evidence-is-reported-as-a-retrya…
vypbot commentedon Oct 17, 2026
Progress: 90% — in progress
Next: Run the required automated gates and verify native acceptance on the current head, including a successful assessment of the complete larger comparison and terminal oversized-evidence handling with prior progress retained.
feature-538-feat-reuse-organization-configuration-and-set-up-selected…
vypbot commentedon Oct 17, 2026
Action required: synchronize the branch
bugfix/547-bugfix-oversized-progress-evidence-is-reported-as-a-retryable-provider-outageis 44 commits behind its parent branchdevelop. It also contains 1 commit not present in the parent branch.Run
/copilot sync-branchin this conversation to merge the parent changes safely. If Git reports conflicts, the configured fixer agent can resolve eligible files before the verification commands run.Compare parent and working branch
efraespada commentedon Oct 17, 2026
Fixed by #546, merged into develop as 1718068 (validated head 9f7f937).
The native SDD run completes all four bounded source parts, the final assessment and publication with zero Action errors: https://github.com/vypdev/copilot/actions/runs/39079316914. All current-head CI checks pass, including RepoWise and Ubuntu/macOS/Windows package-session validation; 10,268 tests pass and Codecov confirms 100% changed-line coverage. The original bugfix branch is superseded by this merged implementation. Production rollout follows the normal release flow.