-
-
Notifications
You must be signed in to change notification settings - Fork 317
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
Startup error running migrations: table identifier does not refer to an existing ETS table #738
Comments
/cc: @filipecabaco |
opening PR 👀 thank you again for flagging this issues |
@chetan where are you running the image? supabase docker compose or cli? |
ok was able to replicate in the supabase/docker 👍 will test the fix |
Merged 🎉 |
Verified! |
thank you so much for reporting and patience 🙏 |
still encountering this on CLI version |
still present on CLI |
@Silur could you share the command and logs so I can try to replicate it? |
Bug report
Migrations fail to run properly. Appears to be due to the use of
Mix.env()
introduced in #736.I took a look at fixing this but don't know elixir at all. According to the docs,
Mix.env()
shouldn't be used in production code (i.e., outside the build system), but I do see it being used in other places in the codebase. Not sure why it's throwing here and not elsewhere.To Reproduce
Run the latest realtime image
supabase/realtime:v2.25.32
on an existing instance (likely throws on fresh data as well)The text was updated successfully, but these errors were encountered: