Skip to content

fix(tui): lower durable event log level - #36479

Merged
kitlangton merged 1 commit into
v2from
event-log-level
Jul 12, 2026
Merged

kitlangton merged 1 commit into
v2from
event-log-level

Conversation

@kitlangton

@kitlangton kitlangton commented Jul 12, 2026 •

Copy link
Copy Markdown
Contributor

What

1. Before: one durable event becomes N INFO lines
With N connected TUIs, every client writes the same durable event to the shared normal log.

1 durable event
      |
      +-- TUI 1 --> INFO  event { type, aggregateID, seq }
      +-- TUI 2 --> INFO  event { type, aggregateID, seq }
      ...
      +-- TUI N --> INFO  event { type, aggregateID, seq }

shared INFO log: N copies, with growth proportional to connected TUIs

2. After: INFO describes connections; DEBUG carries event metadata
The normal log keeps connection lifecycle messages, while detailed durable-event metadata remains available when DEBUG logging is enabled.

INFO   event stream connecting / connected / disconnected / reconnecting
DEBUG event { type, aggregateID, seq }

shared INFO log: no per-durable-event copies

This supersedes the duplicate durable event logging symptom tracked in #36283.

Fixes #36446

Implementation

  • packages/tui/src/context/sdk.tsx: emit per-durable-event metadata at DEBUG instead of INFO.
  • packages/tui/test/cli/tui/use-event.test.tsx: assert that durable event diagnostics use the DEBUG level.

Scope

This does not change event delivery, SSE subscriptions, durable event contents, or connection lifecycle logging.

Testing

  • cd packages/tui && bun run test test/cli/tui/use-event.test.tsx (6 passed, 0 failed)
  • cd packages/tui && bun typecheck (passed)
  • Push hook: bun turbo typecheck --concurrency=3 (31 successful, 31 total)
  • git diff --check (passed)

@kitlangton
kitlangton merged commit 02e2277 into v2 Jul 12, 2026
12 checks passed
@kitlangton
kitlangton deleted the event-log-level branch July 12, 2026 01:37
jinhuang712 pushed a commit to jinhuang712/opencode that referenced this pull request Sep 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant