tree cafa6688d5256cd0eff11f48be531ac038d4a00a
parent 37ca1e1fdc374f56de7387ef00ab1909d0a0fa6d
author Luca Milanesio <luca.milanesio@gmail.com> 1749981825 +0100
committer Luca Milanesio <luca.milanesio@gmail.com> 1750155969 -0700

Do not fail reindexing changes when the patch-sets aren't replicated yet

Depending on how replication is configured, the changes' /meta refs
could be replicated before their associated patch sets. Every time a
change is replicated, the pull-replication plugin emits a
fetch-ref-replicated event related to the change's refs.

When creating a new change, two refs are replicated:
1. refs/changes/<NN>/<NNNN>/1 (first patch-set of the change)
2. refs/changes/<NN>/<NNNN>/meta (change meta-ref)

When the above refs are replicated out of order, with 2. replicated
before 1., then the multi-site plugin tried to reindex the change in an
inconsistent state, throwing a "missing unknown" error and resulting
with a stale index.

Instead of reacting only to 'meta' refs replication, consider all the
refs' replications events associated with a change and ignore the
Indexing errors associated with a missing or unknown SHA1.

Bug: Issue 425059627
Change-Id: I9a6337c1cecb52df832d64b2c7bb30e97ba7916a