tree 280c11bf34acd3eb8f9c1cff7ce98885a6f8889f
parent b0b89a2278b7e696b185fa7295d3f78784f89fef
author Prudhvi Akhil Alahari <prudhvi.alahari@linaro.org> 1664991313 +0530
committer Prudhvi Akhil Alahari <prudhvi.alahari@linaro.org> 1665069737 +0530

prolog_rules cache: only use memoryLimit from cache.projects

Before this change, prolog_rules was pointing to all cache.projects
settings. As prolog_rules cache is not a LoadingCache and Gerrit fails
to start [1] if we've set `cache.projects.refreshAfterWrite`.

The prolog_rules cache never meant to copy all the settings from
`cache.projects` except for `memoryLimit`. Fix this issue by using
`cache.projects.memoryLimit` only when `cache.prolog_rules.memoryLimit`
is not available.

[1]
 [Guice/ErrorInCustomProvider]: IllegalStateException:
  refreshAfterWrite requires a LoadingCache
  at CacheModule.bindCache(CacheModule.java:188)
      \_ installed by: GerritGlobalModule -> PrologModule
      -> RulesCache$RulesCacheModule
  at RulesCache.<init>(RulesCache.java:107)
      \_ for 5th parameter machineCache
  at GerritGlobalModule.configure(GerritGlobalModule.java:248)
  while locating RulesCache

Release-Notes: Settings in cache.prolog_rules now work if available
Change-Id: If74ed1db64dd220db77995a186912a35b1ca73f0