An "invalid response was received from the upstream server" error when querying auth

如果你在向 Supabase Auth 发出请求时看到“从上游服务器收到无效响应”错误，这可能意味着相应的服务已宕机。确认这一点的一种方法是访问日志浏览器，查看 auth 日志，看是否有以下行的错误：

🌐 If you are observing an "invalid response was received from the upstream server" error when making requests to Supabase Auth, it could mean that the respective service is down. One way to confirm this is to visit the logs explorer and look at the auth logs to see if there are any errors with the following lines:

• running db migrations: error executing migrations/20221208132122_backfill_email_last_sign_in_at.up.sql

我们目前正在调查一个问题，即负责跟踪 Auth（auth.schema_migrations）执行的迁移的表没有被正确恢复，这导致服务会重试这些迁移。在这种情况下，非幂等的迁移会出现问题。

🌐 We're currently investigating an issue where the tables responsible for keeping track of migrations ran by Auth (auth.schema_migrations) are not being restored properly, which leads to the service(s) retrying those migrations. In such cases, migrations which are not idempotent will run into issues.

我们在这里记录了一些遇到这个问题的迁移及其对应的解决方法：

🌐 We've documented some of the migrations that run into this issue and their corresponding fix here:

认证：operator does not exist: uuid = text#

🌐 Auth: operator does not exist: uuid = text

临时解决方法：通过 SQL 编辑器 运行 insert into auth.schema_migrations values ('20221208132122'); 来解决这个问题。

🌐 Temporary fix: Run insert into auth.schema_migrations values ('20221208132122'); via the SQL editor to fix the issue.

如果你看到的迁移错误看起来不同，请联系 supabase.help 寻求帮助。

🌐 If the migration error you're seeing looks different, reach out to supabase.help for assistance.