supabase / cli / 37829276675
67%
develop: 67%

LAST BUILD BRANCH: gh-readonly-queue/develop/pr-7081-f8250034bddc9fff102ea6d4fb61c667850c7230
DEFAULT BRANCH: develop
Ran
Jobs 1
Files 79
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: 66.737%. Remained the same
37829276675

push

github

web-flow 
fix(cli): classify new local stack failures in telemetry (#7044)

## Summary

**TL;DR** Failures from the new local stack (`supabase stack *`, and
stack-backed `db reset`, `db dump`, `db diff`, `test db` and `functions
serve`) now reach telemetry with a cause. Before, most of them were
reported as one fingerprint per error tag with category `unknown`, so
start and destroy failures couldn't be told apart. A port conflict now
counts as user-actionable only when the user pinned the port.

### Before

```mermaid
flowchart LR
  A["typed failure<br/>port, pull, timeout"] --> B["StackError<br/>message only"]
  B --> C["…StartError<br/>reason unknown"]
  C --> D["tag:ExperimentalStackStartError<br/>category unknown"]
```

### After

```mermaid
flowchart LR
  A["typed failure<br/>port, pull, timeout"] -->|failureKind| B["StackError<br/>kind + reason"]
  B --> C["…StartError<br/>reason stack"]
  C -->|StackError adapter| D["tag:ExperimentalStackStartError:port_conflict<br/>invalid_config"]
```

### Why

Every `@supabase/stack` failure crossed the owner RPC boundary as
message text. The CLI wrapped each one as `reason: "unknown"`, and none
of the `ExperimentalStack*Error` reasons set a fingerprint suffix. As a
result:

- the top new-stack start and destroy errors showed as `unknown`;
- `stack status` "no stack" and real flag errors shared one fingerprint;
- a raw `StackError` that escaped a command was reported as
`tag:unknown`, losing even its tag.

### What changed

- **`@supabase/stack` carries a failure kind.** `failureKind()` derives
a closed `StackFailureKind` from the typed cause chain. It is carried on
`StackError`, each failed composition outcome, the `POST /shutdown`
failure body and the owner readiness line.
- Failure sites that know the cause set the kind explicitly: port
claims, engine command failures, health and startup timeouts, process
exit and stop, artifact preparation, state, owner startup, connection
and exit, and lease conflicts.
- Docker s... (continued)

4097 of 6139 relevant lines covered (66.74%)

7.37 hits per line

Jobs
ID Job ID Ran Files Coverage
1 37829276675.1 79
66.74
GitHub Action Run
Source Files on build 37829276675