i really don't want my web front any making any direct calls to supabase

I think it's going to be a bit more than 30 mins. We realized that it would probably take a bit longer as we need to patch our tests to accomodate our dependency updates. We also want to sanity check our next release so we don't run into problems again! If you urgently need the fix you can go to the

supabase-py

pyproject.toml and change the hash to the latest hash before running install again Here's the relevant section:

[tool.poetry.dependencies]
python = "^3.7"
postgrest-py = {git = "https://github.com/supabase-community/postgrest-py.git", rev = "c8ba57af60202e5cb98a5388a11cda9954cfd75d"}
realtime-py = "^0.1.2"
gotrue = {git = "https://github.com/supabase-community/gotrue-py.git", rev = "9ba3192dbdccd2f02a4819b52dd6cf51095af7e7"}
httpx = ">=0.19,<0.22"

how to i prevent supabase client side from doing automated things i don't want

Can you explain what exactly I have to change and to what?

Sure

I was wondering if I could install an older version which works

yep you could do that too, it just won't have the

match

command

I've updated the hash so if you go do: 1. git clone git@github.com:supabase-community/supabase-py.git 2. Edit

pyproject.toml

with the snippet above 3. Do

poetry install

You should be able to get the latest version of postgrest-py

really don't enjoy how trying to import a type from the supabase-js lib will cause my app to become non-responsive

Ah thanks I’ll try this and get back to you

no idea what i did and no error messages on build or runtime but supabase hosed my app

I changed max rows in API settings but I’m still seeing a cap of 1000 rows on my database. Does it take time to update?

the match command works thanks, let me know when the fix is pushed into production

@User the supabase client will automatically make a refresh request prior to refresh token expiration and update my session. I don't think it's necessary for me to send the refresh token on my own to sign in

Right, if it has a refresh token it should manage the refreshing

the way you made it sound i should have been sending that refresh token with my requests which was causing the client to fail because i was using up the refresh token

max rows not working

@User seems like the first time it auto refreshes the token it completes the call. subsequent times it fails

this thing is so buggy it's ridiculous

is it possible to create multiple organisations with self-host?

Problems with tokens

hey guys! some quick questions: 1) one user just signed up! perfect! can i verify it manual? running in my backend api for example verifyUser()? do we have such function? 2) I tried to generate a link for verify using the generateLink function like this:

const { data: user, error } = await supabase.auth.api.generateLink({
    type: 'invite',
    email: 'test@gmail.com'
  });

But i get an error message like this:

{
  message: 'Could not read body: json: cannot unmarshal object into Go struct field GenerateLinkParams.type of type string',
  status: 400
}

What's wrong? What's the difference beetween signup / invite? Do we have a verify type?

3) How to initialize a session when a user signIn? How the UI (React) can understand if a user is authenticated or not?

Please use threads for your conversations, It's really hard following these conversations when there are multiple people talking about different things. Discord now has threads and anyone can create them.

Questions

is there an easier way to test auth on a local server other then having to change the site url back and forth from the supabase dashboard

Having a table reporting "failed to fetch" consistently.

Completely frozen.

Testing auth

Hello everyone! Has anyone used https://github.com/supabase/pgadmin4/blob/cli-0.0.4/web/cli.py to generate SQL diff? I tried the docker script but i took almost 1 minute to output the diff file, is it normal?

Any way to send custom emails through supabase without using an external smtp service?