Bobbie Soedirgo
Bobbie Soedirgo
Should we do auth first so we can limit the blast radius & not have to be blocked on supautils changes?
Removed the revoke/grant on auth.schema_migrations. `postgres` can already read all tables by way of `pg_read_all_data` through `pg_monitor`
This still needs additional testing, and I'll be having the Auth team test some of the common flows. And yes, we'll backport this to existing projects.
@evelant are you still having this issue? This [setup](https://github.com/soedirgo/my-app) seems to be working as expected for me.
Are you using a `sbp_v0_` access token? The CLI doesn't accept that atm.
Can you try it with `npx supabase login --debug`? (Making sure to mask the actual token)
Can you check the file encoding of your .env file? If you create a file in WSL vs. Windows, do they have different encodings/file endings?
File encodings orthogonal to line endings. You should be able to check for these [like so](https://stackoverflow.com/questions/3710374/get-encoding-of-a-file-in-windows) - not able to do it myself since I don't have a Windows box
The `status` is retrieved directly from the PostgREST response, and `statusText` comes from `fetch` I believe. But I can't reproduce this on Node 18.4.0. Are you also seeing this on...
Hmm, I thought we already do exclude it: https://github.com/supabase/postgres-meta/blob/df5df091c2b33eaea2e747bdb5bce3d18f74dad6/src/server/templates/typescript.ts#L103 Do you have an example schema I could reproduce this with?