Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add ability to trace handshake #64
feat: add ability to trace handshake #64
Changes from 23 commits
8fe4e52
d4ef98b
4a2404a
9b96d65
420c9f8
4a06e7e
81232cc
e8eaeaf
6bd3583
79c9cf0
b2fcbfd
8e6e391
c36b7f1
5ac4cde
fef4a84
93331de
3233f5a
9e245c9
39a9c9a
882725b
866cdb4
90e333a
a3dba34
b37696b
d7a931b
a149648
dd3d3e8
c05ba96
514adf2
46fb370
66762e0
07bcd61
dc5b90d
06b7488
c4fc44a
23539c7
e9c54b3
5c1f86a
b16e276
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These two fields are a bit obscure to me? One of them is the address and the other the endpoint? Maybe call the second one endpoint? Maybe document each field? None of them is super obvious to me. What is protocol? "tcp" or "udp"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one is only the ip address, the other (endpoint) includes the port. proto is either tcp or udp, correct. I'm going to add comments to those.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added documentation
Check warning on line 24 in internal/model/packet.go
GitHub Actions / lint
Check warning on line 25 in internal/model/packet.go
GitHub Actions / lint
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be more clear if
DirectionIncoming
mapped to"incoming"
, but maybe there is a reason by which you are using"recv"
here that I am missing?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
incoming and outgoing is more clear here indeed. I was thinking about what would be serialized in the trace. first I thought receive/send, and later read/write.
beyond any choice, I think the important problem is where the serialization happens. Probably we can just document the integer and let any user-facing string be the responsibility of the tracer.
Check warning on line 60 in internal/model/trace.go
GitHub Actions / lint
Check warning on line 72 in internal/model/trace.go
GitHub Actions / lint