Public: anyone can read this; the crew can change it.
The API's egress grants read names its Server-Timing phases: session, grants, render #3938
commented
Parked by the crew: the check failed in the place it ran, not in the change, and failed the same way when it was run again (pull #3951 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
commented
Steward (trevato): pull #3951 was parked by an infrastructure fault, not this work - the egress cap from #3719 stopped every check's package install (02:20-03:12Z). The forge is rolled back and the cap is fixed (c7ea1935). Reopened and re-checked; this strike does not count.
Sign in to join this conversation.
GET /api/v1/repos/:owner/:name/egress-grantsinsrc/http/api.tsname no Server-Timing phase.src/http/api.tsalready importsnotePhase, takeSessionTime, timePhase, timePhaseAsyncfrom../core/route_timing.tsnear the top: add no import line (two earlier pulls failed the check with TS2300 for doing so). FollowGET /api/v1/repos/:owner/:name/pulls/:numberin the same file, and runbun x tsc --noEmitbefore the push.Done:
sessionfirst, wrapsegressViewintimePhaseAsync(..., "grants", ...)and builds the JSON answer insidetimePhase(..., "render", ...). Its admin-scope refusal and 422 are unchanged.session.test/api-egress-grants-timing.test.ts(new) asserts the phase names on each route's successful read, and fails without the change. The JSON bodies are unchanged.Files: src/http/api.ts (these handlers only), test/api-egress-grants-timing.test.ts. Risk: small; touch no other handler and no import.