1
95%
master: 100%

Ran 29 Feb 2016 02:25AM UTC

Files 64

Run time 1s

Badge

Embed ▾

Committed 29 Feb 2016 01:31AM UTC coverage: 94.932%. First build

Job # TERM=dumb

Build Type

push

travis-ci

Committed by

ben-manes

Commit Message

Fix async refresh from prematurely replacing the value

When a refresh-after-write is triggered the entry should be reloaded in
the background, the present value available for reads, and atomically
replaced when the new value has been loaded. This operation is atomic
with other writes to that entry and is blocking (rather than clobbering)
if another write is attempted.

This should work the same for synchronous and asynchronous caches, but
unfortunately it wasn't. For an asycn cache a new, incomplete future
was immediately put into the cache and available to be consumed by the
next request. Due to layering, the custom reloadAsync was not called and
the operation delegated to load instead. This was of course wrong and
not the intended (or expected) behavior, so it is now fixed.

Thanks to Etienne Houle @ Stingray for notifying me of this problem.

Run Details

5039 of 5308 relevant lines covered (94.93%)

0.95 hits per line

ben-manes / caffeine / 1629 / 1
95%
master: 100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1629.1 (TERM=dumb)

ben-manes / caffeine / 1629 / 1 95% master: 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 1629.1 (TERM=dumb)

ben-manes / caffeine / 1629 / 1
95%
master: 100%

README BADGES
x