Skip to content

Keep trace capture responsive during daemon recovery - #257

Draft
Stephen Belanger (Qard) wants to merge 1 commit into
mainfrom
t3/review-sdk-722-sdk-741
Draft

Stephen Belanger (Qard) wants to merge 1 commit into
mainfrom
t3/review-sdk-722-sdk-741

Conversation

@Qard

Copy link
Copy Markdown
Collaborator

Trace hooks can time out and lose events while the daemon recovers a large backlog. A slow daemon can also be displaced by another process, leaving multiple daemons running. This change lets hooks record events during recovery and gives each daemon endpoint a single owner.

Related: SDK-722 and SDK-741.

Draft for review: overflow recovery preserves order within each session, but cross-session ordering and late Claude transcript observation during shutdown need further validation.

Validation: daemon library, pipeline, and distributed tracing tests; Clippy; Pi and shared client tests; isolated reproductions of the startup timeout and competing daemons.

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant