HIGH: No size limit on deployment logs stored in SQLite #122

New Issue

2026-02-21T09:52:03+01:00

clawbot commented

2026-02-21 09:52:03 +01:00

Bug

Deployment logs are accumulated without any size cap in the logs TEXT column of the deployments table. The deploymentLogWriter flushes buffered build output to the database every second via AppendLog, which concatenates to the existing logs string.

A long build (up to the 30-minute buildTimeout) producing continuous output can generate hundreds of MB in a single row.

Impact

SQLite database file grows unboundedly
Large logs values cause slow queries when loading deployment details
AppendLog re-writes the entire logs column on every flush (read + concat + write), so performance degrades quadratically with log size
Memory pressure when scanning deployment rows

Files

internal/models/deployment.go — AppendLog() concatenates without limit
internal/service/deploy/deploy.go — deploymentLogWriter flushes every second

Suggested Fix

Options (not mutually exclusive):

Cap AppendLog at a maximum size (e.g., 1MB) and truncate oldest lines when exceeded
Store logs only on disk (already done via writeLogsToFile) and keep only a tail/summary in the DB
Stream logs from the file instead of the DB column for the UI

## Bug Deployment logs are accumulated without any size cap in the `logs` TEXT column of the `deployments` table. The `deploymentLogWriter` flushes buffered build output to the database every second via `AppendLog`, which concatenates to the existing logs string. A long build (up to the 30-minute `buildTimeout`) producing continuous output can generate hundreds of MB in a single row. ## Impact - SQLite database file grows unboundedly - Large `logs` values cause slow queries when loading deployment details - `AppendLog` re-writes the entire logs column on every flush (read + concat + write), so performance degrades quadratically with log size - Memory pressure when scanning deployment rows ## Files - `internal/models/deployment.go` — `AppendLog()` concatenates without limit - `internal/service/deploy/deploy.go` — `deploymentLogWriter` flushes every second ## Suggested Fix Options (not mutually exclusive): 1. Cap `AppendLog` at a maximum size (e.g., 1MB) and truncate oldest lines when exceeded 2. Store logs only on disk (already done via `writeLogsToFile`) and keep only a tail/summary in the DB 3. Stream logs from the file instead of the DB column for the UI

clawbot referenced this issue from a commit

2026-02-21 09:57:36 +01:00

fix: add 1MB size limit on deployment logs with truncation (closes #122)

clawbot referenced a pull request that will close this issue

2026-02-21 09:57:56 +01:00

Fix 1.0 audit bugs (closes #120, closes #121, closes #122, closes #123, closes #124, closes #125) #126

clawbot referenced this issue

2026-02-21 16:45:34 +01:00

Fix 1.0 audit bugs (closes #120, closes #121, closes #122, closes #123, closes #124, closes #125) #126

clawbot referenced this issue

2026-02-21 20:45:37 +01:00

Fix 1.0 audit bugs (closes #120, closes #121, closes #122, closes #123, closes #124, closes #125) #126