-
Notifications
You must be signed in to change notification settings - Fork 73
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
Simplify status compression #93
Simplify status compression #93
Conversation
Codecov Report
@@ Coverage Diff @@
## main #93 +/- ##
==========================================
- Coverage 76.15% 74.51% -1.64%
==========================================
Files 22 22
Lines 1661 1562 -99
==========================================
- Hits 1265 1164 -101
- Misses 297 304 +7
+ Partials 99 94 -5
Continue to review full report at Codecov.
|
1f70451
to
9b529f7
Compare
Resolves open-telemetry#101 Status compression was quite complicated and confusing. It used 4 different hashes and lots of code to enable compression and detection of lost messages (during server restarts). We simplified this significantly by doing this instead: - Eliminate all "hash" fields. - Allow omitting the sub-messages of AgentToServer message. When omitted it is implied that previously reported value of the sub-message is current (unchanged). - To detect lost messages have one auto-incremented sequence_num field AgentToServer message. Server can easily detect losses by just keeping the last sequence_num (as opposed to keeping 4 different hashes). Here is a PR that demonstrates how it works: open-telemetry/opamp-go#93 It is more than 100 lines of code removed.
Resolves open-telemetry#101 Status compression was quite complicated and confusing. It used 4 different hashes and lots of code to enable compression and detection of lost messages (during server restarts). We simplified this significantly by doing this instead: - Eliminate all "hash" fields. - Allow omitting the sub-messages of AgentToServer message. When omitted it is implied that previously reported value of the sub-message is current (unchanged). - To detect lost messages have one auto-incremented sequence_num field AgentToServer message. Server can easily detect losses by just keeping the last sequence_num (as opposed to keeping 4 different hashes). Here is a PR that demonstrates how it works: open-telemetry/opamp-go#93 It is more than 100 lines of code removed.
Resolves open-telemetry#101 Status compression was quite complicated and confusing. It used 4 different hashes and lots of code to enable compression and detection of lost messages (during server restarts). We simplified this significantly by doing this instead: - Eliminate all "hash" fields. - Allow omitting the sub-messages of AgentToServer message. When omitted it is implied that previously reported value of the sub-message is current (unchanged). - To detect lost messages have one auto-incremented sequence_num field AgentToServer message. Server can easily detect losses by just keeping the last sequence_num (as opposed to keeping 4 different hashes). Here is a PR that demonstrates how it works: open-telemetry/opamp-go#93 It is more than 100 lines of code removed.
Resolves open-telemetry#101 Status compression was quite complicated and confusing. It used 4 different hashes and lots of code to enable compression and detection of lost messages (during server restarts). We simplified this significantly by doing this instead: - Eliminate all "hash" fields. - Allow omitting the sub-messages of AgentToServer message. When omitted it is implied that previously reported value of the sub-message is current (unchanged). - To detect lost messages have one auto-incremented sequence_num field AgentToServer message. Server can easily detect losses by just keeping the last sequence_num (as opposed to keeping 4 different hashes). Here is a PR that demonstrates how it works: open-telemetry/opamp-go#93 It is more than 100 lines of code removed.
Resolves #101 Status compression was quite complicated and confusing. It used 4 different hashes and lots of code to enable compression and detection of lost messages (during server restarts). We simplified this significantly by doing this instead: - Eliminate all "hash" fields. - Allow omitting the sub-messages of AgentToServer message. When omitted it is implied that previously reported value of the sub-message is current (unchanged). - To detect lost messages have one auto-incremented sequence_num field AgentToServer message. Server can easily detect losses by just keeping the last sequence_num (as opposed to keeping 4 different hashes). Here is a PR that demonstrates how it works: open-telemetry/opamp-go#93 It is more than 100 lines of code removed.
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 comment needs to be adjusted. Otherwise I think this looks great.
Actually, doing a search for |
9b529f7
to
ad590db
Compare
- Eliminate all "hash" fields. - Allow omitting the sub-messages of AgentToServer message. When omitted it is implied that previously reported value of the sub-message is current (unchanged). - To detect lost messages have one auto-incremented sequence_num field AgentToServer message. Server can easily detect losses by just keeping the last sequence_num (as opposed to keeping 4 different hashes).
The following have comments that refer to the Hash field:
|
ad590db
to
471ea2d
Compare
Thanks for the catch. I did a pass over this files. Please check again. |
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.
Looks good, thanks.
Implements spec change open-telemetry/opamp-spec#101