PerUserTopicSubscriptionManager: avoid access token backoff bypassing
RequestAccessToken() has several calling sides and in the old implementation any call would bypass the exponential backoff. The fix is to just exit early if access token request is backed off. This CL also adds test for repeating access token request on failure, which ensures that access token requested again after backoff time and UpdateSubscribedTopics() call doesn't lead to backoff bypassing. Bug: 1020117 Change-Id: I6cd8db430ce32ae54eca60ad2fad321ffb5119a1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2043835Reviewed-by:Marc Treib <treib@chromium.org> Commit-Queue: Maksim Moskvitin <mmoskvitin@google.com> Cr-Commit-Position: refs/heads/master@{#739366}
Showing
Please register or sign in to comment