Refresh Runs
Latest Trigger runs for anomalyco/opencode.
Run #36
completed1m 47s
Started: Mar 21, 2026 at 10:02 PM UTC
Finished: Mar 21, 2026 at 10:04 PM UTC
Run #35
completed2m 0s
Started: Mar 21, 2026 at 4:02 PM UTC
Finished: Mar 21, 2026 at 4:04 PM UTC
Run #34
completed1m 39s
Started: Mar 21, 2026 at 10:02 AM UTC
Finished: Mar 21, 2026 at 10:04 AM UTC
Run #33
completed2m 39s
Started: Mar 21, 2026 at 4:00 AM UTC
Finished: Mar 21, 2026 at 4:03 AM UTC
Run #32
completed3m 48s
Started: Mar 20, 2026 at 10:02 PM UTC
Finished: Mar 20, 2026 at 10:06 PM UTC
Run #31
completed2m 49s
Started: Mar 20, 2026 at 4:04 PM UTC
Finished: Mar 20, 2026 at 4:06 PM UTC
Run #30
completed3m 41s
Started: Mar 20, 2026 at 10:03 AM UTC
Finished: Mar 20, 2026 at 10:06 AM UTC
Run #29
completed1m 10s
Started: Mar 20, 2026 at 4:02 AM UTC
Finished: Mar 20, 2026 at 4:03 AM UTC
Run #28
completed1m 16s
Started: Mar 20, 2026 at 12:08 AM UTC
Finished: Mar 20, 2026 at 12:09 AM UTC
Run #27
completed1m 7s
Started: Mar 19, 2026 at 10:02 PM UTC
Finished: Mar 19, 2026 at 10:04 PM UTC
Run #26
completed27m 39s
Started: Mar 19, 2026 at 8:47 PM UTC
Finished: Mar 19, 2026 at 9:14 PM UTC
Run #25
completed1m 26s
Started: Mar 19, 2026 at 8:39 PM UTC
Finished: Mar 19, 2026 at 8:41 PM UTC
Run #24
completed8m 28s
Started: Mar 19, 2026 at 8:23 PM UTC
Finished: Mar 19, 2026 at 8:32 PM UTC
Run #23
failed29s
Started: Mar 19, 2026 at 8:18 PM UTC
Finished: Mar 19, 2026 at 8:19 PM UTC
batchTriggerAndWait can only be used from inside a task.run()
Run #22
completed8m 36s
Started: Mar 19, 2026 at 8:01 PM UTC
Finished: Mar 19, 2026 at 8:10 PM UTC
Run #21
completed1m 12s
Started: Mar 19, 2026 at 7:57 PM UTC
Finished: Mar 19, 2026 at 7:58 PM UTC
Run #20
completed5m 34s
Started: Mar 19, 2026 at 7:29 PM UTC
Finished: Mar 19, 2026 at 7:35 PM UTC
Run #19
completed13m 10s
Started: Mar 19, 2026 at 6:59 PM UTC
Finished: Mar 19, 2026 at 7:12 PM UTC
Run #18
completed2m 18s
Started: Mar 19, 2026 at 6:49 PM UTC
Finished: Mar 19, 2026 at 6:51 PM UTC
Run #17
failed1m 15s
Started: Mar 19, 2026 at 6:46 PM UTC
Finished: Mar 19, 2026 at 6:47 PM UTC
score-repo-prs failed for repoId=1
Run #16
completed2m 20s
Started: Mar 19, 2026 at 6:32 PM UTC
Finished: Mar 19, 2026 at 6:34 PM UTC
Run #15
failed14m 59s
Started: Mar 19, 2026 at 6:15 PM UTC
Finished: Mar 19, 2026 at 6:30 PM UTC
Marked stale before v6 24h rerun
Run #14
failed6m 22s
Started: Mar 19, 2026 at 6:08 PM UTC
Finished: Mar 19, 2026 at 6:15 PM UTC
Marked stale before v5 full rerun
Run #13
failed1m 47s
Started: Mar 19, 2026 at 5:49 PM UTC
Finished: Mar 19, 2026 at 5:51 PM UTC
Failed query: insert into "pr_issue_links" ("id", "pr_id", "issue_id") values (default, $1, $2) params: 660,601
Run #12
completed1m 37s
Started: Mar 19, 2026 at 4:05 PM UTC
Finished: Mar 19, 2026 at 4:06 PM UTC
Run #11
failed19s
Started: Mar 19, 2026 at 4:03 PM UTC
Finished: Mar 19, 2026 at 4:04 PM UTC
Failed query: insert into "pull_requests" ("id", "repo_id", "github_pr_number", "title", "body", "state", "draft", "author_login", "additions", "deletions", "changed_files", "created_at", "updated_at", "github_url", "linked_issue_numbers_json", "inferred_scope", "inferred_type", "filtered_out", "filtered_reason") values (default, $1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14, $15, $16, $17, $18) on conflict ("repo_id","github_pr_number") do update set "title" = $19, "body" = $20, "state" = $21, "draft" = $22, "author_login" = $23, "additions" = $24, "deletions" = $25, "changed_files" = $26, "updated_at" = $27, "github_url" = $28, "linked_issue_numbers_json" = $29, "inferred_scope" = $30, "inferred_type" = $31, "filtered_out" = $32, "filtered_reason" = $33 returning "id", "repo_id", "github_pr_number", "title", "body", "state", "draft", "author_login", "additions", "deletions", "changed_files", "created_at", "updated_at", "github_url", "linked_issue_numbers_json", "inferred_scope", "inferred_type", "filtered_out", "filtered_reason" params: 1,14326,fix: switch SQLite from WAL to DELETE journal mode to prevent corruption,### Issue for this PR Closes #14194 ### Type of change - [x] Bug fix - [ ] New feature - [ ] Refactor / code improvement - [ ] Documentation ### What does this PR do? SQLite WAL mode uses a shared memory file (`-shm`) via `mmap` to coordinate across processes. Docker bind mounts on macOS don't reliably propagate `mmap` or `fcntl` locks, so two instances sharing `~/.local/share/opencode/` silently corrupt the database. This switches `journal_mode` from WAL to DELETE (eliminating the `-shm` file entirely), replaces `wal_checkpoint(PASSIVE)` with `locking_mode = EXCLUSIVE` (so the second instance gets `SQLITE_BUSY` instead of `SQLITE_CORRUPT`), and updates `json-migration.ts` which was re-setting journal mode to WAL during bulk inserts. No performance impact — opencode uses one connection per process, so WAL's concurrent-read advantage was unused. ### How did you verify your code works? - Ran `bun dev` locally with the pragma changes, sessions create and update normally - Typecheck passes across all packages - With two instances on the same DB, the second gets a clear `SQLITE_BUSY` error after `busy_timeout` (5s) instead of `SQLITE_CORRUPT` ### Screenshots / recordings _Not a UI change._ ### Checklist - [x] I have tested my changes locally - [x] I have not included unrelated changes in this PR,open,false,theabecaster,3,3,2,2026-02-19T19:40:04.000Z,2026-03-19T15:32:59.000Z,https://github.com/anomalyco/opencode/pull/14326,[14194],unknown,unknown,false,,fix: switch SQLite from WAL to DELETE journal mode to prevent corruption,### Issue for this PR Closes #14194 ### Type of change - [x] Bug fix - [ ] New feature - [ ] Refactor / code improvement - [ ] Documentation ### What does this PR do? SQLite WAL mode uses a shared memory file (`-shm`) via `mmap` to coordinate across processes. Docker bind mounts on macOS don't reliably propagate `mmap` or `fcntl` locks, so two instances sharing `~/.local/share/opencode/` silently corrupt the database. This switches `journal_mode` from WAL to DELETE (eliminating the `-shm` file entirely), replaces `wal_checkpoint(PASSIVE)` with `locking_mode = EXCLUSIVE` (so the second instance gets `SQLITE_BUSY` instead of `SQLITE_CORRUPT`), and updates `json-migration.ts` which was re-setting journal mode to WAL during bulk inserts. No performance impact — opencode uses one connection per process, so WAL's concurrent-read advantage was unused. ### How did you verify your code works? - Ran `bun dev` locally with the pragma changes, sessions create and update normally - Typecheck passes across all packages - With two instances on the same DB, the second gets a clear `SQLITE_BUSY` error after `busy_timeout` (5s) instead of `SQLITE_CORRUPT` ### Screenshots / recordings _Not a UI change._ ### Checklist - [x] I have tested my changes locally - [x] I have not included unrelated changes in this PR,open,false,theabecaster,3,3,2,2026-03-19T15:32:59.000Z,https://github.com/anomalyco/opencode/pull/14326,[14194],unknown,unknown,false,
Run #10
completed1m 13s
Started: Mar 19, 2026 at 3:57 PM UTC
Finished: Mar 19, 2026 at 3:58 PM UTC
Run #9
failed7m 56s
Started: Mar 19, 2026 at 3:49 PM UTC
Finished: Mar 19, 2026 at 3:57 PM UTC
Cancelled stale run before redeploy test
Run #8
failed2m 15s
Started: Mar 19, 2026 at 3:45 PM UTC
Finished: Mar 19, 2026 at 3:47 PM UTC
analyze-pr failed for prId=454
Run #7
failed1m 5s
Started: Mar 19, 2026 at 3:41 PM UTC
Finished: Mar 19, 2026 at 3:42 PM UTC
analyze-pr failed for prId=449
Run #6
failed33s
Started: Mar 19, 2026 at 3:36 PM UTC
Finished: Mar 19, 2026 at 3:36 PM UTC
Parallel waits are not supported, e.g. using Promise.all() around our wait functions.
Run #5
failed19s
Started: Mar 19, 2026 at 3:22 PM UTC
Finished: Mar 19, 2026 at 3:22 PM UTC
Failed query: insert into "pr_features" ("id", "pr_id", "has_linked_issue", "linked_issue_count", "closes_issue_count", "human_pr_comment_count", "human_issue_comment_count", "pr_reactions_count", "issue_reactions_count", "title_matches_conventional", "has_verification_steps", "has_ui_proof", "possible_ai_slop_heuristic", "size_bucket", "content_hash", "created_at", "updated_at") values (default, $1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14, default, $15) on conflict ("pr_id") do update set "has_linked_issue" = $16, "linked_issue_count" = $17, "closes_issue_count" = $18, "human_pr_comment_count" = $19, "human_issue_comment_count" = $20, "pr_reactions_count" = $21, "issue_reactions_count" = $22, "title_matches_conventional" = $23, "has_verification_steps" = $24, "has_ui_proof" = $25, "possible_ai_slop_heuristic" = $26, "size_bucket" = $27, "content_hash" = $28, "updated_at" = $29 params: 441,false,0,0,0,0,0,0,false,false,false,false,unknown,d64663659f653105458732d8c562f643bd3605eea423b4cc330b3898625b8be0,2026-03-19T15:22:42.250Z,false,0,0,0,0,0,0,false,false,false,false,unknown,d64663659f653105458732d8c562f643bd3605eea423b4cc330b3898625b8be0,2026-03-19T15:22:42.250Z
Run #4
failed3m 3s
Started: Mar 19, 2026 at 4:04 AM UTC
Finished: Mar 19, 2026 at 4:07 AM UTC
GitHub request failed (404) /repos/anomalyco/opencode/issues/43335: {"message":"Not Found","documentation_url":"https://docs.github.com/rest/issues/issues#get-an-issue","status":"404"}
Run #3
failed17s
Started: Mar 19, 2026 at 2:51 AM UTC
Finished: Mar 19, 2026 at 2:52 AM UTC
Parallel waits are not supported, e.g. using Promise.all() around our wait functions.
Run #2
failed8m 49s
Started: Mar 19, 2026 at 12:42 AM UTC
Finished: Mar 19, 2026 at 12:51 AM UTC
Recovered stale running row after canceled Trigger run
Run #1
completed12m 29s
Started: Mar 19, 2026 at 12:38 AM UTC
Finished: Mar 19, 2026 at 12:50 AM UTC