GenCode, Cache::cleanKey() - Fix deploop during clean initialization #14777
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Suppose you have a clean codebase with no DAO files, and you try to run
xml/GenCode.php
.This currently crashes.
The problem is not symptomatic day-to-day because we commit DAOs, so it's
very rare to run a full/clean initialization. However, it does get in the
way of stress-testing the correctness of GenCode.
These are the steps I've used to try
GenCode
with a (relatively) clean slate:Before
Running
setup.sh
above crashes:Since 76e697a,
CRM_Utils_Cache::create()
callsCRM_Core_BAO_Cache::cleanKey()
. However, the classCRM_Core_BAO_Cache
cannot be loaded because its parent (CRM_Core_DAO_Cache
) does not yet exist.After
CRM_Core_BAO_Cache::cleanKey()
is migrated toCRM_Utils_Cache::cleanKey()
.CRM_Utils_Cache::create()
no longer loadsCRM_Core_BAO_Cache
orCRM_Core_DAO_Cache
. Thus, it works.