-
Notifications
You must be signed in to change notification settings - Fork 119
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
3. Cleanup internal network request handler, fix unused request logging #3295
Conversation
Codecov Report
@@ Coverage Diff @@
## main #3295 +/- ##
==========================================
+ Coverage 77.18% 77.34% +0.16%
==========================================
Files 265 265
Lines 31462 31415 -47
==========================================
+ Hits 24283 24298 +15
+ Misses 7179 7117 -62 |
I made this medium priority, because it could block ticket #3234 |
09c749b
to
c28fd01
Compare
19f5f3d
to
11a4017
Compare
c28fd01
to
1153aa2
Compare
11a4017
to
f84edc8
Compare
f84edc8
to
e7598a0
Compare
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.
LGTM, the code is cleaner. 👍 I just wasn't sure about the unused messages.
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 great. The new enum adds more semantics to the code.
Co-authored-by: Marek <mail@marek.onl>
The Google Cloud build failed due to a network error on a server we don't control:
So I'll just admin-merge when the rest of CI passes. |
Motivation
In PRs #3293 and #3294, we modify Zebra's internal request handling so it is simpler and more reliable.
This PR removes some workarounds and duplicate code that aren't needed any more.
Solution
Review
This PR is ready for review, but it's based on PR #3294, so we should keep it in draft until that PR merges.
@upbqdn can review this PR.
Reviewer Checklist
I've tested this PR locally, and the regression in the address book metrics stays resolved.
It's hard to test this PR, because we don't have a lot of connection state handling tests. We should have better tests after we implement #1592.