GET /invite/:id passes the path parameter straight into a query on a UUID column. When the id isn't a valid UUID, Postgres returns an invalid-input error rather than sql.ErrNoRows, and the handler panics (cmd/web/main.go, around line 271), so the response is 500.
Reproduction: GET /invite/not-a-uuid returns 500. An unknown but well-formed UUID correctly returns 404.
Expected: 404 for any id that doesn't name an unused invitation. Other handlers that take a UUID path parameter probably behave the same way, so they're worth checking when this is fixed.
Pinned by the skipped test TestE3_InviteInvalidUUID in e2e/accounts_test.go (W3).
GET /invite/:idpasses the path parameter straight into a query on a UUID column. When the id isn't a valid UUID, Postgres returns an invalid-input error rather thansql.ErrNoRows, and the handler panics (cmd/web/main.go, around line 271), so the response is 500.Reproduction:
GET /invite/not-a-uuidreturns 500. An unknown but well-formed UUID correctly returns 404.Expected: 404 for any id that doesn't name an unused invitation. Other handlers that take a UUID path parameter probably behave the same way, so they're worth checking when this is fixed.
Pinned by the skipped test
TestE3_InviteInvalidUUIDine2e/accounts_test.go(W3).