Bug: `supabase db remote commit` stuck if database contains additional schema

[kaleabmelkie]

Bug report

Describe the bug

supabase db remote commit stuck at 0% progress if a new schema is added to the database.

To Reproduce

Steps to reproduce the behavior:

1. Create a new project on app.supabase.io
2. Run the following SQL:

CREATE SCHEMA my_schema

3. Create a new local project with supabase init
4. Run supabase db remote set <REMOTE_URL> -- grab the remote URL from your app.supabase.io dashboard
5. Run supabase db remote commit

Step 5 won't finish. It's stuck at 0% progress (and the label "Committing changes on remote database as a new migration..." is above it).

I've tried it numerous times with the same outcome.

And, if I remove the schema (or never created it in a fresh setup) it will complete the operation in a few minutes.

Expected behavior

supabase db remote commit should finish generating the migrations.

Screenshots

System information

• OS: macOS 12.4 (M1 Pro)
• Version of supabase-cli: 0.26.1
• Version of Node.js: 16.15.1