New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 856723 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Do not cache gitiles requests on refs

Project Member Reported by robert...@chromium.org, Jun 26 2018

Issue description

Our gitiles client should only cache calls that will not change. Such as the details of a specific commit, or the commits between specific commits. 'specific' meaning 'identified by a given commit hash' and not identified by a ref or a tag.

The reason is, when we need to get data on a ref (such as master) we need the most recent data possible, and not data that was cached some time before.
 

Sign in to add a comment