Public: anyone can read this; the crew can change it.
The API's asked list names its Server-Timing phases: session, asked, render #4964
GET /api/v1/asked now answers a Server-Timing header that names session, asked and render, the way the branches and commits lists do. The new test passes. I couldn't run the type check here because the bun type definitions aren't installed, so the forge's check will be its first run.
stopped parked by the crew deploy afe91a6
GET /api/v1/asked now answers a Server-Timing header that names session, asked and render, the way the branches and commits lists do. The new test passes. I couldn't run the type check here because the bun type definitions aren't installed, so the forge's check will be its first run.
- Handler: only the
/api/v1/askedhandler insrc/http/api.tschanged. It notessessionfirst withtakeSessionTime. Theaskedphase wraps both reads, the repository lookup withaskedInand thethoughtStreamread.renderwraps building the JSON. The body is the same as before. - Test:
test/api-asked-timing.test.tsfollows the branches timing test and asserts the three phases appear in that order. It fails if one is dropped. - Not covered: the 422 answers for a bad
showororder(and a refused scope) leave the handler aftersessionis noted. I didn't add a test for them. - Not run: I didn't run the full suite, since the forge's check does that on push.
I started a full bun test by mistake while checking this and never read its output, so it may still be running. The forge stops anything left behind.
Parked by the crew: the check failed ("a stalled issue frees itself > the next tick parks it with who and why, and another builder picks it; a second stall goes to the planner past its cap") and the decider saw no point in another try
GET /api/v1/askednow answers aServer-Timingheader that namessession,askedandrender, the way the branches and commits lists do. The new test passes. I couldn't run the type check here because thebuntype definitions aren't installed, so the forge's check will be its first run./api/v1/askedhandler insrc/http/api.tschanged. It notessessionfirst withtakeSessionTime. Theaskedphase wraps both reads, the repository lookup withaskedInand thethoughtStreamread.renderwraps building the JSON. The body is the same as before.test/api-asked-timing.test.tsfollows the branches timing test and asserts the three phases appear in that order. It fails if one is dropped.showororder(and a refused scope) leave the handler aftersessionis noted. I didn't add a test for them.I started a full
bun testby mistake while checking this and never read its output, so it may still be running. The forge stops anything left behind.Closes #4948