TUI event replay mutation and byte budget fixes
Cluster 108141. Data as of
Nothing open on GitHub. Fix merged in #131327 on 3 Oct 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #131327. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #131327. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where TUI event replay was retaining mutable event object graphs and not properly isolating replayed events from the caller's live parameters. The work involves detaching replay from caller state and freezing payloads within a defined byte budget.
Open issues0
Open PRs0
Fixes on record
-
#131327 fix(tui): keep event replay detached from the caller's live params
files:
tests/tui_gateway/test_tui_gateway_event_replay.py,tui_gateway/event_replay.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#108143 fix(tui): freeze event replay payloads within byte budget · merged via another change →
#131327
Closed issues · 1
- Closed#108141[Bug]: TUI event replay retains mutable event object graphs outside its byte budget
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #131327
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 3 Oct 2026