supabase / cli / 28587111804
65%
develop: 65%

LAST BUILD BRANCH: gh-readonly-queue/develop/pr-5622-5a0e4a9383482808007fb6c1261b79157ee5ff5b
DEFAULT BRANCH: develop
Ran
Jobs 1
Files 229
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: 65.019%. Remained the same
28587111804

push

github

web-flow 
fix(cli): port db pull initial pull to native pg_dump; fix non-interactive confirm hangs (#5725)

## What changed

`db pull`'s initial-migra path (no local migrations, migra engine) is
now native — it no longer delegates to the bundled Go binary. It seeds
the migration file with a native `pg_dump` of the remote schema, then
appends the migra diff, mirroring Go's `dumpRemoteSchema` +
`diffRemoteSchema(nil)` + `swallowInitialInSync` /
`ensureMigrationWritten`.

The pg_dump machinery is hoisted out of `db/dump/` into
`db/shared/legacy-pg-dump.{scripts,env,run}.ts` and shared by `db dump`
and `db pull`; `db dump` is refactored onto the new shared
`legacyStreamPgDump` runner (no behavior change).

## Non-interactive confirm-prompt hang fix

A new `db pull` live test surfaced a real, pre-existing bug: in **text
mode on a non-TTY stdin** (CI/piped), a confirm prompt **blocks
forever** — clack's `confirm` never resolves without a keypress, so the
intended `Effect.orElseSucceed` default never fires. Go's
`console.PromptYesNo` returns the prompt's default on a non-terminal
without blocking. The handlers now gate on the `Tty` service and take
Go's default before prompting, matching the canonical legacy pattern
(`secrets/unset`, `projects/delete`).

Fixed in the three commands that shared this latent hang:

| Command | Prompt | Non-TTY default |
| --- | --- | --- |
| `db pull` | "Update remote migration history table?" | `true`
(proceeds) |
| `config push` | per-service "Keep it enabled?" / "push `<svc>`
config?" | `true` (proceeds) |
| `logout` | "Do you want to log out?" | `false` (cancels) |

Each gets non-TTY integration coverage; the `db pull` no-hang behavior
is also proven end-to-end by the live test.

## Why

`db dump` is already a native pg_dump port, so the dependency `db pull`
was waiting on (its `"needs pg_dump — delegate to Go"` comment) is gone.
This removes the last Go delegation from the common `db pull` path.

## Still delegated

`db pull --exper... (continued)

11007 of 16929 relevant lines covered (65.02%)

10.44 hits per line

Jobs
ID Job ID Ran Files Coverage
1 28587111804.1 229
65.02
 GitHub Action Run
Source Files on build 28587111804