Skip to content

R-00374 r8: terminate chat drain and over-budget ticks - #30

Merged
Go1c merged 1 commit into
mainfrom
feat/r-00374-tick-cap
Sep 2, 2026
Merged

R-00374 r8: terminate chat drain and over-budget ticks#30
Go1c merged 1 commit into
mainfrom
feat/r-00374-tick-cap

Conversation

@Go1c

@Go1c Go1c commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

R-00374 r8 · terminate chat drain and over-budget ticks (RM-00011)

  • Baseline origin/main: e28d2bb1f97673256d9156a57d25a2d0d101bdeb
  • Head: 24a2838d1f90dbf75d0aac0bd576223f5fae7701
  • Independent review: 通过(无 P0 / P1)

Why

R-00376 live9: after r7 socket hold, drain_chat_event_deltas blocked on recv_text until 101. Playwright window 33; replay hung ~21 min until killed. apply_pending_chat_ticks could also continue forever if pending ≥ 64 did not fall.

What

Non-blocking try_recv_text + 50ms drain deadline. apply_pending stops on pending > 64, !tick.ok, or pending not falling. Host refuses Runtime RunTick above 64. Keep r7 release.flag hold.

Verify

  • dispatcher review-tree cargo: lib 93 / architecture 19 / host 14 / wire 10
  • spec-lint OK (reviewer)

Known gaps

  • Live 11-scenario not re-run in this PR; dispatcher rebuilds replay and resumes R-00376.
  • 11-scenario CI FAILURE is not SUCCESS. MVP C# host policy red is N-13.

Drain Room chat.event with non-blocking recv and a deadline so wait_for_observed can return. Stop apply_pending when pending does not fall or tick.ok is false, and refuse RunTick of more than 64 wire chats. Keep r7 release.flag hold.
@Go1c
Go1c merged commit 3c65343 into main Sep 2, 2026
2 of 4 checks passed
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