supabase / cli / 30300334660
65%
develop: 65%

LAST BUILD BRANCH: gh-readonly-queue/develop/pr-6014-14c7b44c0b8a7bd4f7804e0576a0c74f6ff45df4
DEFAULT BRANCH: develop
Ran
Jobs 1
Files 230
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.288%. Remained the same
30300334660

push

github

web-flow 
fix(cli): suppress the --debug hint when a confirmation prompt is declined (#5946)

## What changed

When a confirmation prompt is declined, the Go CLI prints only a red
`context canceled` on stderr and exits 1 — `recoverAndExit`
(`apps/cli-go/cmd/root.go:287-303`) explicitly skips the
`SuggestDebugFlag` fallback for `errors.Is(err, context.Canceled)`. The
TS text `Output.fail` renderer appended the fallback hint for every
suggestion-less error, including cancellations, so every prompting
command (`logout`, `db push` (3 prompts), `db reset`, `migration
fetch`/`repair`/`down`, `functions deploy --prune`, `gen signing-key`,
`secrets unset`, `projects delete`, `branches create`, `bootstrap`)
printed:

```
context canceled
Try rerunning the command with --debug to troubleshoot the error.   ← spurious
```

This PR mirrors Go's guard at the render boundary:

- New shared sentinel `CONTEXT_CANCELED_MESSAGE` in
`apps/cli/src/shared/output/errors.ts` — the byte-for-byte render of
Go's `context.Canceled`.
- The text-layer `fail` (`apps/cli/src/shared/output/output.layer.ts`)
skips the debug-hint fallback when the normalized message equals the
sentinel. The explicit-suggestion branch stays first, matching Go
printing a pre-set `utils.CmdSuggestion` even for canceled errors.
- All 14 cancellation construction sites (12 files: the legacy decline
paths above plus `shared/functions/deploy.ts`) now reference the
constant instead of an inline literal, so the sentinel is single-sourced
like Go's.
- `LEGACY_LOGOUT_CANCELLED_MESSAGE` is folded into the shared constant,
and the documented intent in `logout.errors.ts` (which already described
the Go behavior this PR implements) now matches reality.

## Why the fix is shared rather than legacy-scoped

The failure-rendering seam (`shared/cli/run.ts` `handledProgram` →
`Output.fail`) is shell-agnostic, and `next/` genuinely shares a
cancellation producer: `shared/functions/deploy.ts` (used by `next
functions deploy --prune`) ... (continued)

11257 of 17242 relevant lines covered (65.29%)

10.51 hits per line

Coverage Regressions

Lines Coverage ∆ File
2
82.41
 0.0% internal/storage/rm/rm.go
Jobs
ID Job ID Ran Files Coverage
1 30300334660.1 230
65.29
 GitHub Action Run
Source Files on build 30300334660