Skip to content

Improve TCP pipe direction logging#190

Open
loriopatrick wants to merge 2 commits into
masterfrom
t3code/b7176b17
Open

Improve TCP pipe direction logging#190
loriopatrick wants to merge 2 commits into
masterfrom
t3code/b7176b17

Conversation

@loriopatrick

@loriopatrick loriopatrick commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add Debug to PipeDirection and introduce helpers for naming the read source and write destination.
  • Replace generic TCP pipe log messages with direction-aware messages that clearly state which peer was read from or written to.
  • Downgrade expected shutdown/read/write failure paths to debug logging and add trace logging for successful forwarded chunks.

Testing

  • Not run (PR content generation only).
  • Reviewed the diff to verify log messages now include pipe direction context and endpoint names.
  • Confirmed no behavior changes beyond logging and message clarity.

@loriopatrick
Improve TCP pipe direction logging
ba1d4f0 
- add direction-aware read/write labels to pipe traces
- downgrade read/write failures to debug and log EOF/cancel context
- trace forwarded chunk activity with byte counts
@loriopatrick
Refine tunnel connection and client tracing
9de6489 
- Reword control, TCP, UDP, and LAN socket logs
- Downgrade expected connection failures to warn/debug
- Add richer context for connection spans and retries
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@loriopatrick