-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
limit the exponential PTO backoff to 60s #3595
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
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.
Can we have a test please? :)
fixed an issue where a large number of lost packets would cause the scaled PTO to rollover/overflow to negative and then zero updating a related test that was using a large constant delay and would run up against the new max pto limit
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. We need the CLA before we can merge this though.
Codecov ReportBase: 85.47% // Head: 85.49% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #3595 +/- ##
==========================================
+ Coverage 85.47% 85.49% +0.02%
==========================================
Files 140 142 +2
Lines 10267 10298 +31
==========================================
+ Hits 8775 8804 +29
- Misses 1107 1109 +2
Partials 385 385
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
@cliffc-spirent Friendly reminder that we still need the CLA. |
@marten-seemann the current status is that the Chief Architect has met with the General Counsel and there are some more internal forms to fill out before the CEO gets to make final approval. I wish I was kidding. |
CLA was submitted Friday, still waiting to hear back from Google. |
@lucas-clemente can you please check the CLA? |
Forced a rescan, but nothing changed. |
It looks like the CLA finally made its way through. |
resolves #3594