silentworks

Just as my computer is downloading the million and one docker containers

This is the direct link to support from the Supabase Dashboard https://supabase.com/dashboard/support/new

No I don't think it has anything to do with your explanation. This whole declarative schema thing is confusing to even me at times.

Give me a minute let me test something out because now even me myself is confused

No only 1 shadow db is ever created

No that's not correct, can you point me to which line in the docs says that.

I think this is where you are getting confused. `/schemas` is not used when creating a shadow db, it's the migrations that are used.

This part of the declarative schemas docs show how https://supabase.com/docs/guides/local-development/declarative-database-schemas#managing-dependencies

You can even state some migrations manually while globbing the rest.

You can make the order deterministic by doing stating them manually https://discord.com/channels/839993398554656828/1492931271679279265/1492937452254396538

The second doc is correct. The first doc is also correct. All diffs are done against a local db.

I'm a little confused, are your using declarative schema's but also creating your own migration files at the same time?

You should create your own post in <#1006358244786196510> about the issue you are having.

Please don't hijack other posts as this is unrelated to OPs issue https://discord.com/channels/839993398554656828/1381261799281786932/1458154821503815792

You can also set the order of the migrations inside of your config.toml file too

But if its migrations, aren't they named with datetime at the beginning? this should prevent wrong loading order. Maybe try adding ordered numbers to the beginning of the filenames and see if that fixes it.

There is no way to instruct migra on what to use? also to be clear, is the issue with seeding or migrations?

Are you still using the same Supabase project? did you only migrate your frontend from Hostinger to Vercel or do you mean you created a new Supabase project through the Vercel market integration and upon adding your edge functions again, when you try to access them you are getting errors?

pg-toolbelt is not used by default when doing diff. You have to pass the --pg-delta flag in order to use it. I would suggest testing it out to see if you get better results with it as the default is `migra` and it has had issues with topological sorting in the past. You can also manually set the seed files loading order in the config

Not sure why I was tagged here? Ibrahim has already escalated this through the same channels I would and there is nothing more I can do other than what he has already done.

<@1327676832195018973> the Supabase team are working to revert this change but do note you should remove the format=webp in your future release of the app. If you don't pass webp it will still automatically transform it to webp if the client (browser) is compatible. You should not explicitly pass this.

Were you caching the requests to the transform endpoint? because it seems the PR I shared was deployed from last week and not today or yesterday.

Ok I've passed the information along to the Supabase team. Hopefully someone will look into it soon.

Do share your ticket reference here when you have opened a support ticket with Supabase and we can push it through the informal path to the Supabase team.

Mods aren't Supabase staff so we have no idea when fixes will happen. This is why I asked for you to raise it with Supabase support as they will know best. You should probably also open an issue on the `supabase/storage` GitHub too as that will help with the correct team seeing it much faster.

I think the bug/change was introduced here https://github.com/supabase/storage/pull/921

Also check your API Gateway logs https://supabase.com/dashboard/project/_/logs/edge-logs and your Storage logs to see if there is anymore details there https://supabase.com/dashboard/project/_/logs/storage-logs

You should open a support ticket with Supabase about this https://supabase.com/dashboard/support/new. They will know best how to handle this.

In my project that hasn't been migrated I get the option to change my JWT secret in order to rotate the legacy keys

The screenshot is stating you have been migrated to the new JWT Signing Keys setup and should no longer be using the Legacy JWT stuff.

Can you take a screenshot of your pro organisation name in the drop down list at the top?

Which framework or library is your website built with? how did you setup Supabase in your project? is there a session created when the user clicks the link in the invite email?

You should state what the errors were and post screenshots of them as this would give more context for someone to be able to help you. Do make sure you block out any sensitive information before posting a screenshot.

Check how many connections are used by the `postgres` role here https://supabase.com/dashboard/project/_/database/roles whenever the issue occurs as you might be maxing out your connections.

OAuth doesn't show up in the UI, it's done via config. Also are you trying to create OAuth server or OAuth client? these are two different things. If you are trying to setup something like GitHub, Google or one of the other OAuth's then this is done via the config.toml file under `auth.external` https://supabase.com/docs/guides/local-development/cli/config#auth.external.provider.enabled

Please don’t tag mods unless you were already in a conversation with them in the same post. This new post has no context to it and you haven’t shared what your error is, but rather an assumption to what could be a solution.

This will automatically reset once your billing cycle has lapsed.

There is a link to a guide in the link that was provided above.

Here is the implementation code for Supabase https://github.com/supabase/supabase-js/blob/master/packages/core/supabase-js/src/lib/fetch.ts#L7. This will be monkey patched by Next.js when you use it, as any `fetch` that is not custom is monkey patched by Next.js. https://nextjs.org/docs/app/api-reference/functions/fetch

Nextjs monkey patches fetch, so it should already be doing the caching and stuff.

That is not possible with the built in ones. You could create your own custom one that uses Google, GitHub, etc.

Are you on the Pro plan or Team plan?

Support answers all requests and they are the only ones who can help you with this.

Have you tried restarting the database? Have you sent in a Supabase support request? https://supabase.com/dashboard/support/new

For the first PR you should go and read the issue first and you will see it is already being addressed. The second issue has been pushed to v3 of the library and won't be added to v2. You should really read the issues before using AI to create PRs without reading them.

Even if they do, the verification link has probably expired by now. I think its only valid for 24 or 48 hours.

The user's id is available in the session when you are authenticated. You can use getUser or getSession. Look at the Supabase Auth docs, its all in there.

Only public schema docs will show up. I don't think there is a way of doing what you are asking here.

Try in a different browser as sometimes this is just a state issue in the frontend.

Please don't double post. Gary has already left an reply here. Do your follow ups in this post.