supabase
Persistent intermittent "Failed SASL Auth" in github actions runner only for organisation transferred project
This seems to only happen on a project that i transferred into my organisation, and not on the project that was created within this organisation. which makes me thing there is something in the organisation transfer process that breaks cli auth to the db.
this error is pretty commonly reported but basically its intermittent and happens semi frequently and recently has started happening about 80% of the time.
it occasionally happens on project link, and occasionally happens on db push (after a successful link)
failed to connect to postgres: failed to connect to host=aws-0-us-west-1.pooler.supabase.com user=cli_login_postgres.*** database=postgres: failed SASL auth (invalid SCRAM server-final-message received from server)
debug logs show it attempting to use the dbpassword and failing multiple times on invalid password.
password is definitely valid and running it again without changing anything can lead to successful authentication
This is also happening intermittently for me, with 0 changes between retries. And I've always owned this project. Happens with many of my projects, I wonder if it has something to do with the fact that it's an older project that was provisioned quite some time ago.
Have the same issue, haven't support project for several month, start working on it again, while doing link it's not asking password anymore, and this error occur
