tree ae3e4096a5aaf5bf472dd16aaae61c93e521744a
parent 441d1ae37b3fd6394efee4b50ab56f3525d55201
author Luca Milanesio <luca.milanesio@gmail.com> 1694226210 +0100
committer Luca Milanesio <luca.milanesio@gmail.com> 1694389339 +0100

Do not cache negative results from open changes / timestamp lookups

When the open changes and ts caches are failing to load their
respective data from the repository, the caching of the failure
may have disruptive consequences.

If the failure was just the result of an intermediate replication
event (e.g. a new patch-set has been been replicated but its associated
/meta is still pending) the negative caching would result in making
the ref not discoverable.

The management of the loading failures from the cache is already
coded in the ForProjectWrapper and therefore there is no need to
duplicate a similar logic in the caches as well.

Bug: Issue 299486879
Change-Id: Ic8015238d1f61ad6c47ebdbf6519533dbfa7ec04