Repository: supabase/cli

Issue #2447: `supabase login` "freezes" terminal and dosen't open browser
Created: 2024-06-22T20:20:18Z
Describe the bug
A clear and concise description of what the bug is.
When running the supabase login command, the terminal freezes, well kinda... It disables in some way the ability to copy the link, and dosen't open it to my default browser. Basically like the "text selection" was disabled.
To Reproduce
Steps to reproduce the behavior:

Install the supabase cli on windows
Make sure you open a windows terminal (not cmd, could not test with that)
Install the cli as per the docs
Run supabase login
Press enter
You can't select the link and it's all broken

Expected behavior
The browser opening, or at least me being able to copy the link.
Screenshots

System information
Rerun the failing command with --create-ticket flag.
The feature didn't work, it ignored the flag when running the command.
Additional context
If applicable, add any other context about the problem here.

Default browser Arc for Windows
Version of supabase-js 1.178.2 (supabase --version)
Version of Node.js v20.9.0
Windows 11

Duplicate issue #2470: Getting started with CLI does not work (start, login)
Created: 2024-06-27T23:44:49Z
Describe the bug
I just started using supabase, and my experience with this CLI has been inauspicious.

supabase login doesn't work for me.. I get the browser opened up with a success message, but back in the terminal I'm stuck on Your token is now being generated and securely encrypted. Waiting for it to arrive.... I was able to get around this by manually creaking a token in the dashboard and supplying it via supabase login --token.
supabase start fails as well (with no error messages). Running with --debug I can see some logs but they are really terribly formatted:

There should be an option to not remove the containers upon failure. But, by running docker container ps before the containers get automatically removed I was able to docker container attach to see this realtime error:

** (ErlangError) Erlang error: {:erpc, :timeout}
    (kernel 9.2.4) erpc.erl:714: :erpc.call/5
    (stdlib 5.2.3) timer.erl:270: :timer.tc/2
    (realtime 2.29.13) lib/realtime/rpc.ex:37: Realtime.Rpc.enhanced_call/5
    (realtime 2.29.13) lib/realtime/tenants.ex:85: Realtime.Tenants.health_check/1
    nofile:2: (file)
    (stdlib 5.2.3) erl_eval.erl:750: :erl_eval.do_apply/7
    (stdlib 5.2.3) erl_eval.erl:494: :erl_eval.expr/6
[os_mon] memory supervisor port (memsup): Erlang has closed
[os_mon] cpu supervisor port (cpu_sup): Erlang has closed


Unfortunately, this error happens even if I pass -x realtime.
Running the commands with --create-ticket did not output the sys info required below.

To Reproduce
Steps to reproduce the behavior:

Download the CLI and try basic things from the "Getting Started" documentation.

Expected behavior
Things should just work. If they don't, appropriate errors should be visible.
System information
Rerun the failing command with --create-ticket flag.

Ticket ID: none
Version of OS: Arch Linux
Version of CLI: I've tried both the current release 1.178.2 and the beta 1.179.3.
Version of Docker: 26.1.4
Versions of services:

        SERVICE IMAGE      │      LOCAL       │ LINKED
  ─────────────────────────┼──────────────────┼─────────
    supabase/postgres      │ 15.1.1.61        │ -
    supabase/gotrue        │ v2.151.0         │ -
    postgrest/postgrest    │ v12.2.0          │ -
    supabase/realtime      │ v2.29.13         │ -
    supabase/storage-api   │ v1.0.6           │ -
    supabase/edge-runtime  │ v1.54.9          │ -
    supabase/studio        │ 20240422-5cf8f30 │ -
    supabase/postgres-meta │ v0.80.0          │ -
    supabase/logflare      │ 1.4.0            │ -
    supabase/supavisor     │ 1.1.56           │ -
    darthsim/imgproxy      │ v3.8.0           │ -

Additional context
If applicable, add any other context about the problem here.

Browser: Firefox
Version of supabase-js: none
Version of Node.js: not applicable

Closing comment (2024-07-06T15:35:40Z): Updates on this issue:

It might be a duplicate of #2447
I'm still looking into it, but it doesn't seem like a high priority.
It should be fixed by latest realtime image.
If not, it's now possible to disable realtime completely in supabase/config.toml.
This is working as intended because the flag submits a sentry ticket, not to print out the version info.

The problem with --help taking a long time when offline is also resolved in beta release, ie. npx supabase@beta start.