ben-manes / caffeine / #5577

100%

master: 100%

push

github

Publish UPDATED for jcache refresh reloads

The loader adapter had no reload override, so refreshAfterWrite routed
through load(): a refresh of an existing entry published CREATED (never
UPDATED), stamped it with the creation expiry rather than the update
expiry, and — since load runs on the executor thread with no
awaitSynchronous() drain — leaked each synchronous listener's future
into that thread's pending list. Override reload to publish UPDATED
quietly with getExpiryForUpdate; quiet keeps the future off the pending
list, and a background refresh can't meaningfully block a synchronous
listener anyway.

4076 of 4090 branches covered (99.66%)

12 of 19 new or added lines in 2 files covered. (63.16%)

8312 of 8320 relevant lines covered (99.9%)

1.0 hits per line