supabase / cli / 27401190482
65%

DEFAULT BRANCH: develop
Ran
Jobs 1
Files 225
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 64.876% (+0.2%) from 64.676%
27401190482

push

github

web-flow 
fix(cli): auto-retry db dump/pull via the IPv4 pooler on IPv6-only networks (#5493)

Closes
[CLI-1593](https://linear.app/supabase/issue/CLI-1593/improve-db-dump-ipv6-error-guidance)

## What

`supabase db dump` and `db pull` run `pg_dump` inside a Docker
container. Supabase direct database hosts (`db.<ref>.supabase.co:5432`)
are **IPv6-only** unless the IPv4 add-on is enabled, so on environments
without working IPv6 in the container (very common on Docker Desktop for
macOS) the operation failed with an opaque `error running container:
exit 1`.

This PR makes that path **self-healing**: when a remote dump/pull fails
because the direct host is unreachable over IPv6, the CLI transparently
resolves the project's **IPv4 transaction pooler**, warns the user, and
retries once. If no pooler is available it falls back to an actionable
error message pointing at `--db-url`.

## Why

The host running the CLI often *does* have IPv6 (so the pre-flight dial
succeeds and the direct config is selected), but the `pg_dump`
**container** does not — so the failure only surfaces deep inside the
container as a libpq/getaddrinfo error, hidden behind the generic
container exit code. Users were left stuck with no hint, even though a
working IPv4 pooler existed for their project.

## Behavior

```mermaid
flowchart TD
    A["db dump / db pull (remote)"] --> B["Run pg_dump in Docker container<br/>(tee stderr for classification)"]
    B --> C{Succeeded?}
    C -->|yes| OK["Write dump ✓"]
    C -->|no| D{"stderr is an<br/>IPv6 connectivity error?"}
    D -->|no| SUG["Classify error → actionable suggestion"]
    D -->|yes| E{"Host is a direct<br/>db.&lt;ref&gt;.supabase.co?"}
    E -->|no| SUG
    E -->|yes| F{"IPv4 pooler<br/>config resolvable?"}
    F -->|no| SUG2["Suggest --db-url with the<br/>transaction pooler URL"]
    F -->|yes| G["Warn user · reset output ·<br/>retry once via IPv4 pooler"]
    G --> H{Retry succeeded?}
    H -->|yes| OK2["Write dump ✓<br/>(transparent recov... (continued)

10678 of 16459 relevant lines covered (64.88%)

7.21 hits per line

Coverage Regressions

Lines Coverage ∆ File
62
46.38
 3.29% internal/utils/flags/db_url.go
43
54.85
 -1.83% internal/db/pull/pull.go
15
93.64
 0.19% internal/utils/connect.go
14
62.69
 5.31% internal/db/dump/dump.go
4
94.74
 -0.92% internal/testing/apitest/docker.go
3
66.09
 -2.61% internal/debug/postgres.go
2
80.61
 0.0% internal/storage/rm/rm.go
Jobs
ID Job ID Ran Files Coverage
1 27401190482.1 225
64.88
 GitHub Action Run
Source Files on build 27401190482