Visualize Link in logs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 12.4k
- Forks
- 510
- PR merge metrics
- No merged PRs in 30d
Description
For debugging purpose print current chain for proxy
Example:
downstream addr -> proxy port -> link id -> toxic sub 0 -> ... -> proxy port -> upstream
upstream addr -> proxy port -> link id -> toxic sub 0 -> ... -> proxy port -> downstream addr
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names proxy logging and the current proxy chain, but no files or tests. Start by locating the proxy logging and link traversal entry points, then define how the downstream-to-upstream and upstream-to-downstream chains should appear in logs. Done means both directions print the proxy ports, link IDs, toxic subcomponents, and endpoint addresses shown in the example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100