Skip to content

fix(server): log known forge quota pauses without warning stacks - #24608

Open
juliusmarminge wants to merge 16 commits into
mainfrom
takeover/19794-quota-pause-logs
Open

juliusmarminge wants to merge 16 commits into
mainfrom
takeover/19794-quota-pause-logs

Conversation

@juliusmarminge

@juliusmarminge juliusmarminge commented Oct 24, 2026 •

Copy link
Copy Markdown
Member

Known forge quota refusals in background PR discovery and settlement now log one Info line without a stack. Unknown failures, defects and compound causes retain warning stacks. Pause, retry, backfill and settlement behavior is unchanged.

Fixes #19781. Replaces #19794.

Original description by @aravhawk

Problem

Known GitHub quota pauses in thread PR discovery and automatic settlement emit warning stacks on every sweep, even though quota admission already blocks those reads until reset.

Change

Log recognized typed quota pauses as compact Debug records with thread context and a retry time when known. Typed rate-limit refusals without a retry time still log at Debug; an inner typed cause can supply the timestamp. Unexpected failures, defects and compound causes retain warning stacks. The helper applies to discovery group reads, per-thread saved-PR summary reads, and settlement group reads; the per-thread settlement dispatch catch stays unchanged because it performs no GitHub read.

Quota admission, retry scheduling, settlement eligibility, interruption handling and discovery backfill behavior remain unchanged.

Scope and approval

Fixes #19781, with maintainer approval. Credit to aravhawk for the original contribution. Contributor commits are retained, and current main is integrated by merge.

Verification

  • Reduced nine PR-added cases to six service cases: wrapped discovery pause, unexpected warning, saved-PR summary pause, and settlement pause with a provider timestamp, no timestamp, or an inner typed timestamp. Main's branch-retention tests remain intact.
  • Genuine before-fix/inverse probes failed on the expected log-level differences. Both affected service test files pass all 48 tests on the final implementation head.
  • Scoped server typecheck, lint, formatting and diff checks pass. Lint retains one pre-existing unused-variable warning.
  • This changes server logging only. Tests inject actual typed errors through service dependencies; no live GitHub quota exhaustion, provider calls, user database writes or UI proof is claimed.

Fresh complete independent Claude Opus 5.5 and GPT 6.1 Sol reviews approve 1d98d5a564.

Implementation: Claude Fable 5.1. Minimal tests and independent review: Claude Opus 5.5. Coordination and independent review: GPT 6.1 Sol, through T3 Code.

Takeover

Credit to @aravhawk for the original contribution; the author’s commits are retained. This replacement uses Info and a single text record because the pretty logger spreads structured context over multiple lines.
Forge-owned driver classifiers also cover initial refusals, including Bitbucket 429 body-read failures. Duplicate timestamp tests were replaced with service regressions for previously missed real error types.

Evidence

Before: 76da264a0c. After: bcfa2526f1.
Fixture matrix · Complete paired transcripts and reproduction scripts · Independent audit.

Linux x86_64, Node v26.12.1, real source dev server/workers/pretty logger, fresh temporary homes. APP+STUB fetches loopback 429/502 responses and constructs typed failures; real forge HTTP/admission is bypassed. HARNESS rows call the classifier directly. No live data, real quota exhaustion or browser use.

Matrix row / fixture Before After Proof
1 Wrapped admitted pause, grouped discovery Warn + stack One Info line + reset APP+STUB
2 Unknown grouped discovery failure Warn + stack Warn + stack APP+STUB
3 Paused saved-PR read Warn + stack One Info line + reset APP+STUB
4 Unknown saved-PR failure Warn + stack Warn + stack APP+STUB
5 Quota settlement, branch and saved forms Warn + stack One Info line + reset APP+STUB
6 Unknown settlement, branch and saved forms Warn + stack Warn + stack APP+STUB
7 Refusal without reset Warn + stack One Info line, no invented time APP+STUB
8 Reset on an inner typed cause Warn + stack One Info line + inner reset APP+STUB
9 Generic provider refusal with reset Warn + stack One Info line + reset HARNESS
10 Initial GitHub refusal Warn + stack One Info line + reset APP+STUB
11 Initial GitCafe 429 Warn + stack One Info line, no invented time APP+STUB
12 Unknown error mentions rate limit Warn + stack Warn + stack HARNESS
13 Quota failure plus unknown failure Warn + causes Warn + causes HARNESS
14 Quota failure plus defect Warn + causes Warn + causes HARNESS
15 Typed pause as a defect Warn + cause Warn + cause HARNESS
16 Other initial refusals across six forges Warn + stack One Info line, optional reset HARNESS
17 Other forge errors, including body-read 502 Warn + stack Warn + stack HARNESS
18 Invalid/out-of-range reset Warn + stack One Info line, invalid time omitted HARNESS
19 Bitbucket body-read 429 Warn + stack One Info line + reset APP+STUB

Paired app records: 18 distinct baseline Warn records become 14 single-line Info and 4 unknown Warn records. Repeated sweeps are also retained. Paired classifier records: 25 cases pass. State proof: nine equal thread payloads excluding timestamps, four saved references retained, no settlement or provider runs.

What else changed: expected log level and format only. No UI change. All 19 required matrix rows are covered.

Verification log
  • Three independent Codex/Claude review rounds. Fixed initial GitHub/GitCafe refusals, nonthrowing reset formatting, and the Bitbucket body-read variant. Both reviewers returned MERGE in round three at the final head.
  • PR-added cases: 6 → 4 after pruning duplicate reset-time cases, then 3 service regressions added for missed initial refusal shapes: 7 final cases. Affected files pass 12 + 23 = 35 tests.
  • Final gate: 42/42 tests across the two services, registry and quota admission; formatting and server typecheck pass. Changed-file lint has only the pre-existing unused layer warning.
  • Independent proof audit: SUFFICIENT, rows 1–19; corrected publication verified and withdrawn exports return 404. Rebuilt an affected app case with three empty payload deltas and all nine state payloads matching.
  • CI: pending on the replacement PR at publication; no merge performed.
  • Unverified surfaces: none among changed server logging paths. Real forge HTTP/admission and real reset timing were not exercised; APP+STUB explicitly bypasses them. Web, desktop and mobile rendering are unchanged.
  • Temporary servers stopped; all proof scripts uploaded, none committed. Original contributor head stayed unchanged throughout the takeover.
  • Models/harness: Claude Opus 5.5 for tests and implementation; GPT 6.1 Sol and Claude Opus 5.5 for independent reviews; GPT 6.1 Sol for evidence and proof audit, coordinated through the Codex harness in T3 Code.

Fixes #19781

aravhawk and others added 13 commits October 15, 2026 00:28
Keeps main's branch-retention discovery tests alongside the reduced
quota-pause log regressions, and restores the plain warning in the
per-thread settle dispatch catch, which performs no GitHub reads.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
… PR summary reads

A rate-limited PullRequestProviderError is a known pause even when GitHub omits the
reset headers, so the helper now classifies it as a pause and only reports retryAt
when the provider error or a typed inner pause carries one. The per-thread discovery
catch that consumes saved pull request summary failures now logs through the same
helper, so a paused summary read no longer emits a warning stack per thread.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Replace the original PR's log tests with the minimum behavioural set:
a paused branch lookup and a paused saved pull request read log one
Info line without a stack, an unexpected lookup failure keeps its Warn
stack, and a rate-limited settlement read without a reset time logs
Info and settles nothing. The Info assertions stay red until the
implementation moves from Debug to Info.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A known rate-limit pause repeats on every pull request sweep until the
reset time, so it now logs a single Info line with the retry time and
thread ids instead of a Warn stack. The pretty console logger spreads
structured fields over several lines, so the pause line carries its
context as text. Unknown failures keep their Warn stack.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GitHub's GitHubApiRateLimitError and GitCafe's 429 GitCafeApiError reach the
pull request sweeps wrapped in SourceControlProviderError before the host
pause starts, so they still warned with a stack. Each source control driver
now recognizes its own refusal through an optional rateLimitRefusal hook,
and the shared failure logger asks the registry instead of naming forge
types. A reset time that is not a valid date is left out of the line.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Bitbucket reports a 429 whose body could not be read as
BitbucketResponseBodyReadError. Its own throttle and pull request mapper
already treat that as a rate limit, but the driver's rateLimitRefusal hook
only matched BitbucketResponseError, so the sweep still warned with a stack.
The hook now matches both.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions github-actions Bot added the vouch:trusted Author is trusted by repo permissions or the VOUCHED list. label Oct 24, 2026
@github-actions github-actions Bot added the size:L 100-499 changed lines (additions + deletions). label Oct 24, 2026
macroscopeapp[bot]
macroscopeapp Bot previously approved these changes Oct 24, 2026
@macroscopeapp

macroscopeapp Bot commented Oct 24, 2026 •

Copy link
Copy Markdown
Contributor

Approvability

Verdict: Approved at 248e6f9

Macroscope's review found this PR approvable — Known forge quota pauses now produce compact Info lines instead of warning stacks during background PR discovery and settlement. Unexpected failures retain warning stacks, and retry, quota handling and settlement behavior are unchanged.

You can add or adjust custom eligibility rules. Learn more.

@github-actions

github-actions Bot commented Oct 24, 2026 •

Copy link
Copy Markdown
Contributor

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider Metric Main baseline This PR Impact PR ceiling
Codex Total thread wire 5.0 KiB 5.0 KiB 0 B (0.0%) 6.8 KiB ✅
Codex Thread snapshot wire 3.8 KiB 3.8 KiB 0 B (0.0%) 4.9 KiB ✅
Codex Live turn WebSocket wire 1.2 KiB 1.2 KiB 0 B (0.0%) 2.0 KiB ✅
Codex Live turn WebSocket decoded 21.5 KiB 21.5 KiB 0 B (0.0%) 24.4 KiB ✅
Codex Live turn messages 1 1 0 (0.0%) 8 ✅
Claude Total thread wire 5.0 KiB 5.0 KiB 0 B (0.0%) 6.8 KiB ✅
Claude Thread snapshot wire 3.8 KiB 3.8 KiB 0 B (0.0%) 4.9 KiB ✅
Claude Live turn WebSocket wire 1.2 KiB 1.2 KiB 0 B (0.0%) 2.0 KiB ✅
Claude Live turn WebSocket decoded 21.9 KiB 21.9 KiB 0 B (0.0%) 24.4 KiB ✅
Claude Live turn messages 1 1 0 (0.0%) 8 ✅

Other scenarios

All 64 scenario measurements match main.

All 64 scenario measurements
Provider Scenario Metric Main baseline This PR Impact PR ceiling
Codex short turn resume WebSocket decoded 10.5 KiB 10.5 KiB 0 B (0.0%) 12.7 KiB ✅
Codex short turn resume WebSocket messages 2 2 0 (0.0%) 2 ✅
Codex long turn running, cold open HTTP decoded 281.7 KiB 281.7 KiB 0 B (0.0%) 302.7 KiB ✅
Codex long turn running, cold open rows 75 75 0 (0.0%) 75 ✅
Codex long turn running, history page HTTP decoded 92.4 KiB 92.4 KiB 0 B (0.0%) 107.4 KiB ✅
Codex long turn running, history page rows 75 75 0 (0.0%) 75 ✅
Codex long turn finished, cold open HTTP decoded 381.5 KiB 381.5 KiB 0 B (0.0%) 410.2 KiB ✅
Codex long turn finished, cold open rows 151 151 0 (0.0%) 151 ✅
Codex long turn finished, socket cold open WebSocket decoded 381.6 KiB 381.6 KiB 0 B (0.0%) 410.2 KiB ✅
Codex long turn finished, socket cold open WebSocket messages 2 2 0 (0.0%) 2 ✅
Codex long turn finished, socket cold open rows 151 151 0 (0.0%) 151 ✅
Codex long turn finished, work page HTTP decoded 186.2 KiB 186.2 KiB 0 B (0.0%) 200.2 KiB ✅
Codex long turn finished, work page rows 150 150 0 (0.0%) 150 ✅
Codex idle thread resume WebSocket decoded 65 B 65 B 0 B (0.0%) 200 B ✅
Codex idle thread resume WebSocket messages 1 1 0 (0.0%) 1 ✅
Codex fleet shell snapshot HTTP decoded 42.4 KiB 42.4 KiB 0 B (0.0%) 53.7 KiB ✅
Codex fleet shell snapshot rows 27 27 0 (0.0%) 27 ✅
Codex fleet shell subscribe WebSocket decoded 65 B 65 B 0 B (0.0%) 200 B ✅
Codex fleet shell subscribe WebSocket messages 1 1 0 (0.0%) 1 ✅
Codex fleet shell resume check HTTP decoded 18 B 18 B 0 B (0.0%) 100 B ✅
Codex fleet shell resume check rows 0 0 0 0 ✅
Codex stale shell reload HTTP decoded 42.4 KiB 42.4 KiB 0 B (0.0%) 53.7 KiB ✅
Codex stale shell reload rows 27 27 0 (0.0%) 27 ✅
Codex stale shell resume WebSocket decoded 140 B 140 B 0 B (0.0%) 400 B ✅
Codex stale shell resume WebSocket messages 2 2 0 (0.0%) 2 ✅
Codex stale todo list cold open HTTP decoded 72.4 KiB 72.4 KiB 0 B (0.0%) 83.0 KiB ✅
Codex stale todo list cold open rows 75 75 0 (0.0%) 75 ✅
Codex stale todo list cold open nodes 2 2 0 (0.0%) 4 ✅
Codex stale todo list cold open subagents 2 2 0 (0.0%) 4 ✅
Codex stale todo list cold open plans 1 1 0 (0.0%) 2 ✅
Codex stale todo list cold open providerTurns 1 1 0 (0.0%) 2 ✅
Codex stale todo list cold open checkpoints 1 1 0 (0.0%) 2 ✅
Claude short turn resume WebSocket decoded 10.6 KiB 10.6 KiB 0 B (0.0%) 12.7 KiB ✅
Claude short turn resume WebSocket messages 2 2 0 (0.0%) 2 ✅
Claude long turn running, cold open HTTP decoded 283.3 KiB 283.3 KiB 0 B (0.0%) 302.7 KiB ✅
Claude long turn running, cold open rows 75 75 0 (0.0%) 75 ✅
Claude long turn running, history page HTTP decoded 93.4 KiB 93.4 KiB 0 B (0.0%) 107.4 KiB ✅
Claude long turn running, history page rows 75 75 0 (0.0%) 75 ✅
Claude long turn finished, cold open HTTP decoded 384.2 KiB 384.2 KiB 0 B (0.0%) 410.2 KiB ✅
Claude long turn finished, cold open rows 151 151 0 (0.0%) 151 ✅
Claude long turn finished, socket cold open WebSocket decoded 384.3 KiB 384.3 KiB 0 B (0.0%) 410.2 KiB ✅
Claude long turn finished, socket cold open WebSocket messages 2 2 0 (0.0%) 2 ✅
Claude long turn finished, socket cold open rows 151 151 0 (0.0%) 151 ✅
Claude long turn finished, work page HTTP decoded 188.1 KiB 188.1 KiB 0 B (0.0%) 200.2 KiB ✅
Claude long turn finished, work page rows 150 150 0 (0.0%) 150 ✅
Claude idle thread resume WebSocket decoded 66 B 66 B 0 B (0.0%) 200 B ✅
Claude idle thread resume WebSocket messages 1 1 0 (0.0%) 1 ✅
Claude fleet shell snapshot HTTP decoded 43.0 KiB 43.0 KiB 0 B (0.0%) 53.7 KiB ✅
Claude fleet shell snapshot rows 27 27 0 (0.0%) 27 ✅
Claude fleet shell subscribe WebSocket decoded 66 B 66 B 0 B (0.0%) 200 B ✅
Claude fleet shell subscribe WebSocket messages 1 1 0 (0.0%) 1 ✅
Claude fleet shell resume check HTTP decoded 18 B 18 B 0 B (0.0%) 100 B ✅
Claude fleet shell resume check rows 0 0 0 0 ✅
Claude stale shell reload HTTP decoded 43.0 KiB 43.0 KiB 0 B (0.0%) 53.7 KiB ✅
Claude stale shell reload rows 27 27 0 (0.0%) 27 ✅
Claude stale shell resume WebSocket decoded 140 B 140 B 0 B (0.0%) 400 B ✅
Claude stale shell resume WebSocket messages 2 2 0 (0.0%) 2 ✅
Claude stale todo list cold open HTTP decoded 73.4 KiB 73.4 KiB 0 B (0.0%) 83.0 KiB ✅
Claude stale todo list cold open rows 75 75 0 (0.0%) 75 ✅
Claude stale todo list cold open nodes 2 2 0 (0.0%) 4 ✅
Claude stale todo list cold open subagents 2 2 0 (0.0%) 4 ✅
Claude stale todo list cold open plans 1 1 0 (0.0%) 2 ✅
Claude stale todo list cold open providerTurns 1 1 0 (0.0%) 2 ✅
Claude stale todo list cold open checkpoints 1 1 0 (0.0%) 2 ✅

Baseline: 00f617d · PR result: 248e6f9 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

  • Codex decoded thread snapshot: 108.5 KiB
  • Claude decoded thread snapshot: 108.8 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

@coderabbitai

coderabbitai Bot commented Oct 24, 2026 •

Copy link
Copy Markdown
Contributor

Explain Change →

No actionable comments were generated in the recent review.

Walkthrough

Source-control drivers now identify host rate-limit refusals and expose optional retry timestamps. Thread pull-request discovery and settlement use shared failure logging that reports recognized rate limits at info level and retains warning logs for other failures.

Changes: Rate-limit refusal logging

Layer / File(s) Summary
Refusal contract and provider recognition
packages/source-control-core/src/server/driver.ts, packages/source-control-*/src/server/driver.ts, packages/source-control-bitbucket/src/server/driver.test.ts, packages/source-control-github/src/server/driver.test.ts
The driver contract adds an optional rate-limit refusal callback. Azure DevOps, Bitbucket, Forgejo, GitCafe, GitHub, and GitLab drivers recognize provider-specific rate limits. Bitbucket and GitHub tests cover refusal results and retry timestamps.
Failure classification and logging
apps/server/src/orchestration-v2/threadPullRequestFailure.ts, apps/server/src/orchestration-v2/threadPullRequestFailure.test.ts
The helper checks paused errors, provider refusals, and driver refusals in single-failure cause chains. Tests cover info-level rate-limit logs and warning-level logs for other failures.
Thread service integration
apps/server/src/orchestration-v2/ThreadPullRequestService.ts, apps/server/src/orchestration-v2/ThreadSettlementService.ts
Pull-request discovery and settlement pass failure causes and affected thread IDs to the shared logging helper.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Change: Bug fix · Severity of issue fixed: Low

Suggested reviewers: t3dotgg, yash-singh1

Merge Risk: Minimal · up to 248e6

This change reduces log noise for known forge quota pauses and keeps warning stacks for unexpected failures. No merge-blocking risk was identified.

Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title names the main change: known forge quota pauses are logged without warning stacks. The raw summary confirms that recognized rate-limit failures in discovery and settlement now log one Info l…
Description check Passed The description follows the repository template. It has a Problem section, a Change section, a Scope section that links issue #19781 and states maintainer approval, and a Verification section with spe…
Linked Issues check Passed Issue #19781 asks that expected, already-known GitHub quota pauses in thread PR discovery and automatic settlement stop repeating full warning stacks. Unexpected failures must keep useful warning stac…
Out of Scope Changes check Passed Changes outside apps/server are the optional rateLimitRefusal hook in packages/source-control-core/src/server/driver.ts and per-forge implementations in the Azure DevOps, Bitbucket, Forgejo, GitCafe, …
Full details: Title check

Explanation

The title names the main change: known forge quota pauses are logged without warning stacks. The raw summary confirms that recognized rate-limit failures in discovery and settlement now log one Info line, and unknown failures keep warnings. The title is short and conventional, and it does not describe unrelated work.

Full details: Description check

Explanation

The description follows the repository template. It has a Problem section, a Change section, a Scope section that links issue #19781 and states maintainer approval, and a Verification section with specific tests, matrix rows, and observed results. It also states what was not checked, which the template requires. The template's opening guidance asks for a conventional title in plain language, and the title meets that. The description is long and includes some process detail, such as model names and review history, but the required content is present and specific.

Full details: Linked Issues check

Explanation

Issue #19781 asks that expected, already-known GitHub quota pauses in thread PR discovery and automatic settlement stop repeating full warning stacks. Unexpected failures must keep useful warning stacks. The issue allows the pause to be 'summarized or throttled'. Evidence at head 248e6f9: apps/server/src/orchestration-v2/threadPullRequestFailure.ts defines logThreadPullRequestFailure. rateLimitPause() inspects only causes with exactly one failure reason, walks Error.cause without revisiting errors, and recognizes SourceControlRateLimitPausedError, a rate-limited PullRequestProviderError, and driver rateLimitRefusal results. A recognized pause logs one Effect.logInfo line with the thread IDs and the reset time when it parses. Other causes log Effect.logWarning with Cause.pretty. The PR summary states that ThreadPullRequestService (grouped and per-thread discovery catches) and ThreadSettlementService (group-read failure) route through this helper. [#19781] Requirement mapping: expected pauses are summarized as one Info line per group per sweep. This meets the 'summarized' option. Unknown failures, defects, and compound causes keep Warn with stacks. Pause, retry, and settlement logic are not changed per the PR description. Unresolved uncertainty: the head commit 248e6f9 (subject: 'test(server): quota pause logs tested at the classifier, not the sweep') changes tests. The incremental diff could not be read because changed blobs are missing from the checkout, so the test-only nature and the final test content are not verified here. Stack review evidence is unavailable; no stack objectives were assessed.

Full details: Out of Scope Changes check

Explanation

Changes outside apps/server are the optional rateLimitRefusal hook in packages/source-control-core/src/server/driver.ts and per-forge implementations in the Azure DevOps, Bitbucket, Forgejo, GitCafe, GitHub, and GitLab drivers. The helper calls these hooks via BUILT_IN_SOURCE_CONTROL_DRIVER_LIST to recognize initial forge refusals that reach the catch before quota admission wraps them. The PR summary maps these hooks to matrix rows 10, 11, 16, and 19, so they support the logging objective of [#19781]. Each hook returns undefined for unrecognized errors, so unknown failures keep warning stacks. The issue names apps/server as its scope, and these package changes extend recognition beyond that path. They serve the same log-level behavior and do not alter admission, retry, settlement eligibility, or backfill. No contrary evidence was found. Unresolved uncertainty: the driver diffs at the current head could not be read directly because changed blobs are missing from the checkout. This verdict relies on the helper source at head and the PR summary for each hook.

Finishing Touches

Generate unit tests (beta)

  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Usage-based review receipt

Note

This review was completed with usage-based billing: files reviewed beyond your plan's included limits are billed at $0.25/file. View usage-based billing.

Recent review info

Run configuration

Commits

Reviewing files that changed from the base of the PR and between 999345e and 248e6f9.

Files selected for processing: 5

  • apps/server/src/orchestration-v2/ThreadPullRequestService.ts
  • apps/server/src/orchestration-v2/ThreadSettlementService.ts
  • apps/server/src/orchestration-v2/threadPullRequestFailure.test.ts
  • packages/source-control-bitbucket/src/server/driver.test.ts
  • packages/source-control-github/src/server/driver.test.ts

Limit details: You’ve used all 10 included reviews currently available.

@juliusmarminge juliusmarminge added bugfix Fix PR opened by an issue lead; enters the PR loop pr:gate-failed A land gate failed pr:needs-verification Reviewed and green; needs a run on a desktop, Android or iOS device and captures posted and removed pr:needs-verification Reviewed and green; needs a run on a desktop, Android or iOS device and captures posted pr:gate-failed A land gate failed labels Oct 25, 2026
…pause-logs

Resolves conflicts with main's settlement and GitHub driver changes, and moves
the forge failure log tests onto main's harness (SecureRandom, Path, and
getPullRequestSnapshot).

AI-assisted; verified with the tests and tools listed above.
@juliusmarminge

Copy link
Copy Markdown
Member Author

The automated pipeline stopped on this pull request and will not merge it:

the capture step could not show the problem on the base commit, so there is nothing to prove fixed.

Checked the required exhausted-account prerequisite through GitHub's REST rate_limit endpoint. REST had 11,184/20,000 requests remaining; GraphQL had 19,899/20,000 points remaining. Neither met the quota-pause prerequisite. Did not deliberately exhaust the shared account.

It stays open for a person to finish or close.

@juliusmarminge juliusmarminge added the takeover:in-progress A takeover lead is working on this PR label Nov 13, 2026
juliusmarminge and others added 2 commits November 13, 2026 16:44
The sweep-level tests rebuilt the whole discovery and settlement harnesses
to check a one-line log swap, and reached into forge packages by relative
path. Cover the helper's cause walking directly, and each forge's refusal
classifier in its own package.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@macroscopeapp
macroscopeapp Bot dismissed their stale review November 13, 2026 16:49

Dismissing prior approval to re-evaluate 248e6f9

@juliusmarminge juliusmarminge added takeover:blocked Takeover blocked; reason in the PR body and removed takeover:in-progress A takeover lead is working on this PR labels Nov 13, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugfix Fix PR opened by an issue lead; enters the PR loop pr:needs-verification Reviewed and green; needs a run on a desktop, Android or iOS device and captures posted size:L 100-499 changed lines (additions + deletions). takeover:blocked Takeover blocked; reason in the PR body vouch:trusted Author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Known GitHub quota pauses repeatedly log full warning stacks in thread PR discovery and settlement

2 participants