GitLab

AboutResource has an internal caching mechanism, that is only refreshed when
UpdateAboutResource is called. With the introduction of team drives
UpdateAboutResource is no longer called to get the largest change id, which
means that the cached version can become stale. Here we introduce a timer that
will periodically evict that cached version, so that calls to GetAboutResource
will get fresh data from the server.

Bug: 874551
Change-Id: Ib0ed943b2abec95c6d32be17228dd429ffedaea8
Reviewed-on: https://chromium-review.googlesource.com/1189684
Commit-Queue: Stuart Langley <slangley@chromium.org>
Reviewed-by: Sam McNally <sammc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#586191}