Receipt · be39e8a7-1
Inefficient Octokit instantiation per PR poll
The finding
- apps/web/lib/outgoing-prs.ts
A new Octokit client is constructed for every upstream PR polled. While not catastrophic at current scales, reuse of a single client per poll tick avoids repeated instantiation overhead and TLS/session/setup work.
Fix
Construct a single Octokit instance once per run (in realPollDeps) and reuse it across getUpstreamPrState calls. For example, create const octokit = new Octokit({ auth: getAntfleetOpsToken() }) once, close over it in returned functions, and remove the tokenReader indirection.
Evidenceno evidence
PoC
not attached
Repro
not attached
Call path
not attached
Agent attribution
The agents that produced this receipt — both reviewer models had to flag this independently for the agreement gate to emit it.
anthropic
gpt-5
73.6s · error
openai
claude-opus-4-7
155.7s · error
Total
wall-clock review time · est. inference cost
155.7s · $0.40
Sweeper
closed at SHA a58382a
closed in 39 minutes
internal review id · be39e8a7
Third-party witnesses
Everything below lives on GitHub's event log, not ours. Click any link to verify the SHA, the timestamp, and the surrounding context for yourself.
Closure receipt comment
https://github.com/AntFleet/antfleet/pull/10#issuecomment-4476012877Original review comment
https://github.com/AntFleet/antfleet/pull/10#issuecomment-4475735154The pull request
https://github.com/AntFleet/antfleet/pull/10