-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when running npm run setup (setup:seed) #63
Comments
Any chance you already have a user with email hello@supabase.com in auth dashboard? (maybe you already try to seed and try again?) Something goes wrong in the script and it hides supabase error 😅. will try to test asap ;) |
nope, no users at all, either in public/users or auth/users |
I’m far from my computer, but you can try to add a .catch(console.error) line 31 of https://github.com/rphlmr/supa-fly-stack/blob/main/app/database/seed.server.ts |
const newUserId... returns 'fetch failed'
|
I have push a better error handling in seed script. Shadow DB is no more required if you just have created a Supabase project, so I have also remove this part. The error you linked says that fetch failed (the Supabase SDK internal fetch). Could be a temporary issue from Supabase?
PS : I can't reproduce from a fresh install :/ |
Aha, you don’t need the shadow db?
How do I remove it? I’m new to Postgres
On Fri, 10 Feb 2023 at 17:28 Raphaël Moreau ***@***.***> wrote:
I have push a better error handling in seed script.
Shadow DB is no more required if you just have created a Supabase project,
so I have also remove this part.
The error you linked says that fetch failed (the Supabase SDK internal
fetch). Could be a temporary issue from Supabase?
—
Reply to this email directly, view it on GitHub
<#63 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7MD4KS3TPI3FQNOE23B5TWWZUCJANCNFSM6AAAAAAUXA5BUI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
/Johan
|
If it's just a new project, easiest is to delete it and recreate 😅 Or keep it and just remove the env in the prisma file like the commit i did. |
Alright, thanks! |
I hope it's fine for you ;) Feel free to reopen if you still have an issue. |
This is what I get:
Any clues?
I followed every step and created the shadow db as described in supabase docs
The text was updated successfully, but these errors were encountered: