fix: preserve SSH forwarding half-close semantics - #34
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthrough
ChangesTCP half-close forwarding
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~20 minutes Change: Bug fix Sequence Diagram(s)sequenceDiagram
participant bicopy
participant copyAndHalfClose
participant TCPConnections
bicopy->>copyAndHalfClose: Start two directional copies
copyAndHalfClose->>TCPConnections: Copy data
copyAndHalfClose->>TCPConnections: CloseWrite after EOF
copyAndHalfClose-->>bicopy: Return copyResult
bicopy->>TCPConnections: Close both connections after completion or error
Merge Risk: ⚪ Minimal · up to The forwarding change has regression coverage for request/response half-closes and no actionable current-head risk remains. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches✨ Simplify code
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 |
Summary
Verification
go vet ./...go test ./...go test -race ./...git diff --checkCodeRabbit local review completed; its read-deadline finding was addressed in the follow-up test commit.
Summary by CodeRabbit