Anonymous - 2 days ago

Originally posted by: athanclark

It happened again, on PR [#491], whose changes don't touch sign-in (run). This time it failed at a different step, test/passkeys-live-postgres.mjs:284:

page.waitForResponse: Timeout 30000ms exceeded while waiting for event "response"

That step signs out, opens /login with the authenticator refusing, and waits for the autofill's POST /api/auth/passkeys/sign-in to be refused (401). The request never came.

Both failures have the same shape:

  • The steps: each signs out, opens /login, and then the sign-in form never reaches its ready state. The first time the Sign in with a passkey button didn't show; this time the autofill request wasn't sent.
  • What both need: the page's own GET /api/session to answer, with mode login and passkeySignIn.

Two possibilities fit, either of which would point at the session read rather than at passkeys:

  • that read fails or hangs, and the card shows an error or keeps loading;
  • the page lands in another step.

PR [#496] makes the test print the card's text and the session when the button doesn't appear. This second step should print the same when it times out; I'll add that.

🤖 Generated with Claude Code

https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B

 

Related

Tickets: #491
Tickets: #496