Hi. I'm trying to run this super simple sql statement

UPDATE public."Category" SET name_en='Front fender' WHERE "name"='Framskärm'

But I get "An error occurred with your deployment". What am I doing wrong?

I tried to manually update that value on a row using the web interface. Got this

Ran the sql statement again and looked at the logs. I get "canceling statement due to statement timeout"

Hi, I'm trying to use supabase for a discord login with the following function:

js
async function signInWithDiscord() {
  const { user, session, error } = await supabase.auth.signIn({
    provider: 'discord',
  })
}

the problem is that if you call this function when you click a button it's going to open the discord login page and then redirecting you back, but in this way you are never going to get `user `and

session

, is there anyway to retrive those data?

Hmm interesting, since the auth schema has a table called "users" not "profiles" and on that "users" table I don't know of an "inserted_at" key. If you made your own profiles table with an "inserted_at" this would make a bit more sense.

Is there some way to restrict access to Supabase Studio?

Because I'd like to use it for myself, but as far as I can tell it's publicly available to anyone on port 3000

I don't expose that port personally. I could probably IP restrict it but that would get annoying. You could put it behind basic http auth in nginx most likely. Manage the routing with nginx

Alrighty, I’ll figure that out 🙂 thanks!

Ok. I just don’t know of a built in way. Supabase seems to gate using auth0

I noticed today my instance is running on postgresql 12.6, which was released in Feb 2021 and has 6 known security vulnerabilities listed: https://www.postgresql.org/support/security/

what postgresql version are your supabase cloud instances running?

postgresql recommends all users run the latest point release, which is 12.9 for the 12 version series

I think you have to migrate old projects manually https://supabase.com/docs/guides/database

I think the studio runs on "localhost", so it can only be accessed by the user.

It doesn't run on localhost, it binds like everything else

If you open the port then anyone can connect, I've gotten it behind a nginx password thing so I'm super happy 🙂

ic, I thought it shld bind only to localhost 🙂

No worries 🙂

Cloud project dashboard - Settings > API > JWT Secret

This only shows me the option to reveal the token. Do you have one to change it?

Supabase control panel is down? Trying to log in, it does oauth, then, comes back to "Sign in With Github". If I click again, it loops again (ad infinitum). Cleared cookies. Tried a different browser. Same.

Unable to proceed past here, yet, it was working earlier today... Please advise, over.

^ i'm running into the same issue

Well good to know it's not just me, bummerz for team Supabase…

specifically, I'm getting "Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://o398706.ingest.sentry.io/api/5459134/envelope/?sentry_key=caa7db5fc1da4341810a6d56251a951c&sentry_version=7. (Reason: CORS request did not succeed). Status code: (null)."

on both firefox and chromium

(today's my first day trying supabase, so i thought I'd really messed up somehow)

I'm not seeing that in Safari, just a "Failed to load resource yada yada 500"

It's been working great for me... until tonight. Hopefully will be fixed soon.