-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
stats: Improved sequencing documentation for server-side stats events and added tests. #7885
base: master
Are you sure you want to change the base?
Changes from all commits
44abfd0
10f6726
92ec341
71adf5e
8622eab
f291e58
dcb64c1
c157b93
480ce6b
8b90cae
443d960
436bc06
19b4974
53b7249
6a8c733
4a18e7e
fb39711
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -36,7 +36,10 @@ type RPCStats interface { | |
IsClient() bool | ||
} | ||
|
||
// Begin contains stats when an RPC attempt begins. | ||
// Begin contains stats when an RPC attempt begins. This event is called after | ||
// the InHeader event, as headers must be processed before the RPC lifecycle | ||
// begins. | ||
// | ||
// FailFast is only valid if this Begin is from client side. | ||
type Begin struct { | ||
// Client is true if this Begin is from client side. | ||
|
@@ -98,7 +101,9 @@ func (s *InPayload) IsClient() bool { return s.Client } | |
|
||
func (s *InPayload) isRPCStats() {} | ||
|
||
// InHeader contains stats when a header is received. | ||
// InHeader contain stats when the header is received. It is the first event in | ||
// the server after receiving the RPC. It is followed by the OutPayload | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can you clarify what you are asking for here? |
||
// server event. | ||
type InHeader struct { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @RyanBlaney we should just edit the documentation in current struct instead of deleting it entirely and re-creating. Also, restrict the documentation to struct instead of writing the whole sequence. Mentioning that it is the first event on server side after rpc is received is fine. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'll get right to it! Thank you! |
||
// Client is true if this InHeader is from client side. | ||
Client bool | ||
|
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.
nit
InHeader
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.
What specifically is the issue here? Is it related to style?