fix(libsy): client disconnect logging - #555
Conversation
Signed-off-by: Greg Clark <grclark@nvidia.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. WalkthroughThe server now detects buffered handler cancellation after client disconnects. It emits a terminal warning event with status ChangesClient disconnect accounting
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to No actionable merge-blocking risk remains based on the supplied evidence; the PR is merge-ready after normal checks and review. Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Comment |
What
Emit client disconnect metric and ensure processing stops on client disconnect.
This was only reproducible on macOS
Why
The motivation — what problem does this solve, or which ticket does it close?
Closes SWITCH-1218
How tested
uv run ruff check .cleanuv run mypy switchyardcleanuv run pytest tests/greenChecklist
snake_caseof the primary class.switchyard/__init__.py.__all__if intended for downstream use.--helpupdated if customer-facing surface changed.Signed-off-by: Your Name <email>) per the DCO.Notes for reviewers
Anything reviewers should pay extra attention to — risky paths, follow-up tickets, intentional trade-offs.
Summary by CodeRabbit
Bug Fixes
Monitoring