Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
✅ Deterministic PR hygiene checks passed. |
📝 WalkthroughWalkthroughChangesTerminal guard bounds
Estimated code review effort: 3 (Moderate) | ~20 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
✅ READY
Hygiene✅ Deterministic PR hygiene checks passed. |
Carry the bounded-retention fix from #85 (source 51723d6) onto current dev. Preserve upstream passthrough, opt-in, timestamp, and usage behavior; stop retaining after tool activity, substantive text, or replay limits. Add focused boundary regressions and document the retention contract. Co-authored-by: luvs01 <27862058+luvs01@users.noreply.github.com>
|
상류 기존 상류의 heartbeat/tool-delta 통과 처리, 단일 타임스탬프, OpenAI Chat opt-in 동작을 보존하면서 이벤트 수·콘텐츠 보존량 제한과 44개 회귀 검증 사례를 추가했습니다. 게시 커밋: Node 기반 격리 검증은 63 통과 / 0 실패 / 1개 기존 bridge 통합 검증 제외입니다. Bun 전체 검증·타입 검사·CI 통과를 주장하지 않으며, 상류 PR은 해당 검증과 리뷰가 끝나기 전까지 초안 상태입니다. 이 원본 PR은 닫거나 병합하지 않았습니다. |
|
Closing this tracking PR. The terminal guard content retention work was reimplemented against current upstream |
Motivation
donewas observed.Description
MAX_RETAINED_EVENTSandMAX_RETAINED_CONTENT_CHARS, and track retained text/content size while streaming.analysisEnabledflag that is cleared when any bound is exceeded or atool_call_startis seen, and clear the per-turnseenbuffer when analysis is disabled so the guard stops growing memory usage.analyzeTerminalTurnwhenanalysisEnabledis true; otherwise fall back to pass-through behavior and do not attempt continuations.stops retaining events once a streamed answer cannot be a short announcementthat verifies oversized/non-terminal streams are still forwarded to the client but not retained for analysis or continuation.Testing
bun test tests/terminal-guard.test.ts, which passed (15 tests, 0 failures).bun run typecheck, which succeeded.bun run privacy:scan, which succeeded.bun run test; a pre-existing unrelated assertion intests/service.test.tsfailed, so the full suite was not green, but the terminal-guard focused tests and relevant regressions all passed.Summary by CodeRabbit
Bug Fixes
Tests