Skip to content

Promote stage to bkt3 (2026-10-23 evening): t3_get_session on the SQLite reader (#349) - #350

Merged
bk-agent-01 merged 4 commits into
bkmainfrom
promote/stage-2026-10-23b
Oct 23, 2026
Merged

bk-agent-01 merged 4 commits into
bkmainfrom
promote/stage-2026-10-23b

Conversation

@bk-agent-01

Copy link
Copy Markdown
Collaborator

Tushar gave the go on 2026-10-23 in his Manager fork session. His word: "promote".

This PR brings stage (1d8cb7a) to bkmain. The merge commit only joins the histories, and the tree is identical to stage 1d8cb7a.

What it brings

Risk

A bkmain deploy restarts bkt3 and stops every live turn for about 1 minute. Tushar gave the go for this restart. The Manager fork session checks the server deploy and the desktop release after the restart. Earlier today the desktop Build job was cancelled once because no macOS runner took it, so the session reruns that job once if it happens again.

How I tested

🤖 Generated with Claude Code

bk-agent-01 and others added 4 commits October 23, 2026 17:25
getThreadDetailSnapshot, the whole-session read behind the t3_get_session
MCP tool, ran its transaction on the writer. On bkt3 it held the writer, and
so the event loop, for 3.4-5.2 s and caused two of the three freezes in the
first 34 minutes after the 2026-10-23 deploy.

The transcript import still runs first on the writer, because it can write.
The session read then runs under NodeSqliteClient.readOnly on the reader
worker, the same boundary as PR #344.

Refs TEC-1502

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…INSERT writes

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fix(server): t3_get_session reads the session on the SQLite reader
@github-actions github-actions Bot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:XS labels Oct 23, 2026
@bk-agent-01

Copy link
Copy Markdown
Collaborator Author

Merging on Tushar's explicit go of 2026-10-23 ("promote"). Head f9195f84c34cebe23449585bc61eefe10c86b2c1: 20 checks pass and 5 are skipped. The tree is identical to stage 1d8cb7a. This merge restarts bkt3. A check of the deploy and the desktop release is scheduled in the Manager fork session.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XS vouch:trusted PR author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant