tree b62eedd8830874078d42de72bdaaf43694c6f184
parent 39f62a9da2aff9d712077d746997266247a94192
author Jacek Centkowski <geminica.programs@gmail.com> 1671780051 +0100
committer Jacek Centkowski <geminica.programs@gmail.com> 1672322614 +0100

Don't attempt to cache refs containing '[:|@]' in resolve call

The 'ref + ":" + filename' syntax is used to resolve the file's ObjectId
under the specific ref. That attempt fails to succeed in 'exactRef' call
therefore it falls back to the delegate 'resolve' call.
The `ref + "@"` syntax (according to [1]) is used to reach out to a
reflog entry or to a value of ref prior the point in time.
The result (for both cases) is consistent with delegate 'resolve' call
but cycles are wasted on 'exactRef' call that returns 'null'.

This change adds refs that contain '[:|@]' as non cacheable. The check
leverages on Guava's CharMatcher to check all chars in a single input
String's loop.
Note that the CachedRefRepositoryIT was rewritten to work on a
FileRepository so that reflog could be enabled and `@`-related checks
performed.

[1] https://git-scm.com/docs/git-rev-parse#_specifying_revisions

Bug: Issue 16553
Change-Id: Ia86e6bd2c0da4c7eceffc090ad1e7a63d63552fc