tree e2ad8d65495279ba1cfea606ddfb9d0c3a086aca
parent de44654afccc2fd4b5f2e263871d17e930adcb09
author Luca Milanesio <luca.milanesio@gmail.com> 1626209678 +0100
committer Luca Milanesio <luca.milanesio@gmail.com> 1626283042 +0100

Limit returned changes for a triplet without Change-Id

When looking for a single change, do not perform a full scan
of all changes on a repository/branch as they would not identify
a single entry but rather limit the result to just 2 elements,
which would be enough to identify the response.

Fix a bug where invoking the REST-API /changes/repo~branch~ without
mentioning the change-id resulted in the full scan of all changes
on a repository/branch causing a high CPU overload and occupying
the request threads for a long time.

Requesting a single change by NOT specifying its change-id is not
a valid use-case, and it should always return a 404, regardless of
how many changes exist on the project/branch.

Bug: Issue 14785
Change-Id: Ief77d199c917fea8ebaa6ecc44a7b4b2c59d6f4e