Account for fast mono clock when polling in device flow #111
+139
−222
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.
Fixes #108
I've pushed
babakks/test-oauth-polling-2tocli/clito test the changes in this PR/branch.This PR improves the device flow experience to accommodate for edge cases where the monotonic clock (which is the basis for time measurement) runs fast. See the linked issue and cli/cli#9370 for more context.
The summary of the changes are:
slow_downand keep it even if we didn't get moreslow_downs.- If there's a clock drift higher than 5% (abs):- If positive (faster mono), bail out at the 3rdslow_down.- If negative (slower mono), bail out at the 5thslow_down.slow_downbail out with an error message including the measured clock drift.