supabase / cli / 37639532460
67%
develop: 67%

LAST BUILD BRANCH: columferry/cli-2695-develop-target-warning
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
37639532460

push

github

web-flow 
fix(stack): remove database helpers when their owner exits (#7014)

## Summary

**TL;DR:** Database helpers now stay attached to the owning process. If
that process exits or is killed, the Docker client's stdin closes, the
helper exits, and Docker removes the container. A normal `docker stop`
also ends the helper.

### Before

Both shared-volume and per-instance helpers used detached `docker run
-d` containers with a shell that ignored TERM. They could remain after
the owner disappeared, and `docker stop` could not shut them down.

### After

Helpers start with `docker run --rm -i` and wait for a readiness signal
before commands use them. Their shell exits on stdin EOF or TERM.
Existing named helpers are replaced instead of being adopted without an
owner connection. The shared database volume is left intact when a
helper exits.

### What changed

- Give each helper a lifetime scope so its attached Docker client
remains open for as long as the helper is in use, including cleanup
during owner shutdown.
- Preserve startup cleanup when helper creation is interrupted, and
report Docker's startup error when available.
- Cover attached startup, helper scope behavior, and owner SIGKILL
cleanup in the storage and registry tests.

## Linked issue

Closes #6962

---------

Co-authored-by: avallete <andrew.valleteau@supabase.io>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Andrew Valleteau <avallete@users.noreply.github.com>

4097 of 6139 relevant lines covered (66.74%)

7.37 hits per line

Jobs
ID Job ID Ran Files Coverage
1 37639532460.1 79
66.74
GitHub Action Run
Source Files on build 37639532460