Laurence Isla

I could not reproduce the issue. After creating the table and granting select to a non-anonymous user: ```console $ curl "http://localhost:3000/a" -I -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJyb2xlIjoidG9kb191c2VyIn0.YhVX9eNb-mnCdzZAOCB12XxqXcnWNpq5Go8kVyipTH0" HTTP/1.1 200 OK Date:...

PostgREST uses the OpenAPI v2.0 spec where the body doesn't have a `headers` key, it's located in the `parameters` key instead according to https://swagger.io/specification/v2/#fixed-fields. But it seems that the generated...

I've ~~run the tests~~ run the changes and they work successfully for docker postgres 15 beta2 and [beta3](https://hub.docker.com/layers/postgres/library/postgres/15beta3/images/sha256-7e8c76773c37c58e2254a46207381244c921a4e0224669dabea82088498bd3fb?context=explore).

To handle base64 encoded secrets, it also needs `PGRST_JWT_SECRET_IS_BASE64` set to `true` for it to work. Was that configuration enabled?

Oh, then maybe the padding character is missing at the end? Adding `=` to the end of the string may solve the issue. When I delete it, I get the...

Then, maybe try encoding your secret again and update it in the configuration. Perhaps the length it's not a multiple of "4", it throws that error when it's not, according...

Ah, then yes. Using the secret without `=` at the end should do it.

@wolfgangwalther Right, I wasn't clear in that regard. I reproduced this using a Base64 JWT with 64 characters and adding two padding characters (`==`) at the end. These were the...

Some users are used to stored procedures as a way to mutate data without returning values, not necessarily for the need of using nested transactions (e.g. #1739 ). So, even...

Yes, the amd64 image is very small because it is built using nix, generating a static binary that can be executed on a minimal docker image. Unfortunately, we cannot do...