Skip to content

[pull] main from tldraw:main#486

Merged
pull[bot] merged 2 commits intocode:mainfrom
tldraw:main
Apr 7, 2026
Merged

[pull] main from tldraw:main#486
pull[bot] merged 2 commits intocode:mainfrom
tldraw:main

Conversation

@pull
Copy link
Copy Markdown

@pull pull Bot commented Apr 7, 2026

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

…8483)

The Zero backup-monitor polls Litestream's `/metrics` endpoint to
determine the safe replication watermark for changelog pruning. Without
a configured `addr`, Litestream never serves its metrics endpoint, so
the backup-monitor can't reach it (`ECONNREFUSED` on `localhost:4850`).
This means the changelog table never gets pruned — it grew to 6.7GB (75%
of the DB) in 6 days.

This adds `addr: localhost:4850` to the Litestream config so it serves
metrics on the port Zero expects (default port 4848 + 2).

### Change type

- [x] `bugfix`

### Test plan

1. Deploy to staging
2. Verify `curl localhost:4850/metrics` returns litestream metrics from
inside the RM container
3. Monitor changelog table size — should start decreasing as
backup-monitor triggers cleanup

### Release notes

- Fix Zero changelog table growing unbounded by enabling Litestream
metrics endpoint for backup-monitor.

### Code changes

| Section | LOC change |
| ------- | ---------- |
| Apps    | +1 / -0   |
Disables Zero deployment on production branch while we resolve WAL
accumulation and replication slot invalidation issues. The Zero
replication slot was consuming 4GB WAL (hitting `max_slot_wal_keep_size`
limit) and getting invalidated, causing cascading issues including
Supabase restarts and sync-worker slot invalidation.

Staging (`main` branch) continues to deploy Zero normally.

### Change type

- [x] `bugfix`

### Test plan

1. Merge to `main` — staging deploy should still deploy Zero
(`flyio-multinode`)
2. Merge to `production` — should skip Zero deployment entirely

### Code changes

| Section        | LOC change |
| -------------- | ---------- |
| Config/tooling | +1 / -1    |
@pull pull Bot locked and limited conversation to collaborators Apr 7, 2026
@pull pull Bot added the ⤵️ pull label Apr 7, 2026
@pull pull Bot merged commit 196b22a into code:main Apr 7, 2026
@pull pull Bot had a problem deploying to bemo-canary April 7, 2026 21:13 Failure
@pull pull Bot had a problem deploying to deploy-production April 7, 2026 21:13 Failure
@pull pull Bot had a problem deploying to deploy-staging April 7, 2026 21:13 Error
@pull pull Bot had a problem deploying to bemo-canary April 7, 2026 21:13 Failure
@pull pull Bot had a problem deploying to vsce publish April 7, 2026 21:13 Failure
@pull pull Bot had a problem deploying to deploy-staging April 7, 2026 21:13 Failure
@pull pull Bot had a problem deploying to deploy-staging April 8, 2026 00:36 Failure
@pull pull Bot temporarily deployed to e2e-dotcom April 8, 2026 02:36 Inactive
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant