Page MenuHomePhabricator

Improve compatibility of "Config > Cache Status" across APCu versions
ClosedPublic

Authored by epriestley on Aug 8 2018, 6:30 PM.
Tags
None
Referenced Files
F18802901: D19569.id46782.diff
Fri, Oct 17, 8:49 PM
F18701813: D19569.diff
Sat, Sep 27, 9:10 PM
F18679123: D19569.id.diff
Fri, Sep 26, 12:32 AM
F18675244: D19569.diff
Thu, Sep 25, 5:27 PM
F18658628: D19569.diff
Sep 23 2025, 7:34 AM
F18656764: D19569.id46781.diff
Sep 22 2025, 11:23 PM
F18652573: D19569.id.diff
Sep 21 2025, 8:39 AM
F18649804: D19569.id46781.diff
Sep 20 2025, 10:17 PM
Subscribers
None

Details

Summary

Ref T13164. See PHI790. Older versions of APCu reported cache keys as "key" from apcu_cache_info(). APC and newer APCu report it as "info".

Check both indexes for compatibility.

Test Plan
  • Locally, with newer APCu, saw no behavioral change.
  • Will double check on admin, which has an older APCu with the "key" behavior.
  • (I hunted this down by dumping apcu_cache_info() on admin to see what was going on.)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

src/applications/cache/spec/PhabricatorDataCacheSpec.php
118–122

Previously, we would send <unknown-key> into getKeyPattern(), which would turn it into <other-namespace> most of the time, making the problem less obvious. I tweaked this so we retain <unknown-key>.

This revision is now accepted and ready to land.Aug 8 2018, 10:04 PM
This revision was automatically updated to reflect the committed changes.