Supabase client hangs and can't be killed #4302
Description
Describe the bug
Occasionally a command will hang, and hitting Ctrl-C will, instead of killing the command, bring up a prompt to enter your database password. At that point the npx console can't be killed or exiting. The entire terminal window must be closed.
Sample output:
sh-3.2$ supabase migration repair --status reverted 20251013053053
Initialising login role...
Connecting to remote database...
failed to connect to postgres: failed to connect to `host=aws-1-us-west-1.pooler.supabase.com user=cli_login_postgres.mpwtyvmjfazgumpeawvb database=postgres`: tls error (read tcp 192.168.1.244:51282->54.241.91.151:5432: i/o timeout)
Try rerunning the command with --debug to troubleshoot the error.
sh-3.2$
sh-3.2$ supabase migration repair --status reverted 20251013053053
Initialising login role...
failed to connect as temp role: failed to connect to `host=aws-1-us-west-1.pooler.supabase.com user=cli_login_postgres.mpwtyvmjfazgumpeawvb database=postgres`: dial error (dial tcp 54.241.91.151:6543: connect: connection refused)
Retry (3/8): failed to connect as temp role: failed to connect to `host=aws-1-us-west-1.pooler.supabase.com user=cli_login_postgres.mpwtyvmjfazgumpeawvb database=postgres`: dial error (dial tcp 54.241.91.151:6543: connect: connection refused)
Retry (4/8): ^CForgot your password? Reset it from the Dashboard: https://supabase.com/dashboard/project/mpwtyvmjfazgumpeawvb/settings/database
Enter your database password:
To Reproduce
Not deterministically reproducible
Expected behavior
Ctrl-C kills the command.
Screenshots
If applicable, add screenshots to help explain your problem.
System information
sh-3.2$ supabase -v
2.51.0
Additional context
❯ node -v
v24.6.0
❯ npx -v
11.6.1