Skip to content
This repository was archived by the owner on Oct 10, 2025. It is now read-only.

Conversation

@dragarcia
Copy link
Contributor

Should resolve #188. With the new version of the supabase/postgres image, there would be the need to explicitly specify the postgresql.conf location to /etc/postgresql/postgresql.conf.

@dragarcia dragarcia marked this pull request as draft December 3, 2021 05:34
@dragarcia
Copy link
Contributor Author

Tested this repeatedly locally and it seems to be able to yield the same results as when run now in master with the previous version (supabase/postgres:13.3.0). Running npm run t on master already has its own set of errors:
image

Not sure what's different when run over GA. Even increasing the sleep to 2 minutes yield the errors shown.

@dragarcia dragarcia marked this pull request as ready for review December 3, 2021 09:11
@leynier
Copy link

leynier commented Dec 3, 2021

It works fine for me, I tried it with gotrue-py too, thanks a lot. Those errors must be tests that need to be updated.

@J0
Copy link
Contributor

J0 commented Jul 6, 2022

Hey team,

Could we bump this branch when free to sanity check if the tests pass? Should be good to merge after.

Thanks!

@dragarcia dragarcia merged commit cbc147e into master Jul 14, 2022
@dragarcia dragarcia deleted the chore/supabase_postgres_14.1.0 branch July 14, 2022 02:19
@github-actions
Copy link
Contributor

🎉 This PR is included in version 1.22.20 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions
Copy link
Contributor

🎉 This PR is included in version 1.23.0-next.5 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: docker-compose up is failing and causes the tests to fail later

5 participants