ben-manes / caffeine

94%

master: 100%

LAST BUILD ON BRANCH v2.5.4

branch: v2.5.4

CHANGE BRANCH

x

Reset

• v2.5.4
• 05a040c2478341bab8a58a02b3dc1fe14d626d72
• 2.5.6
• Gil
• adaptive
• async-loader
• ben/issue30
• ben/spacing
• buffer
• cache2k
• clockpro
• codeql
• dependabot/github_actions/JetBrains/qodana-action-2023.1.4
• dependabot/github_actions/JetBrains/qodana-action-61b94e7e3a716dcb9e2030cfd79cd46149d56c26
• dependabot/github_actions/codecov/codecov-action-3.1.3
• dependabot/github_actions/github/codeql-action-2.3.4
• dependabot/gradle/com.gradle.common-custom-user-data-gradle-plugin-1.9
• dependabot/gradle/com.gradle.enterprise-3.14
• dependabot/gradle/de.thetaphi-forbiddenapis-3.6
• dependabot/gradle/pmd-7.0.0-rc4
• expiring_map
• expiry
• gil
• gilga
• gradient
• guava
• jctools
• juherr
• master
• memory
• orm
• penalties
• solr
• testng
• tmp
• travis
• v1.0
• v1.0.1
• v1.1.0
• v1.2.0
• v1.3.0
• v1.3.1
• v1.3.2
• v1.3.3
• v2.0.0
• v2.0.1
• v2.0.2
• v2.0.3
• v2.1.0
• v2.2.0
• v2.2.2
• v2.2.4
• v2.3.2
• v2.3.4
• v2.5.2
• v2.5.3
• v2.5.5
• v2.6.1
• v2.7.0
• v2.8.0
• v2.8.1
• v2.8.2
• v2.8.3
• v2.8.4
• v2.8.5
• v2.dev
• v3.0.5
• v3.0.6
• v3.1.0
• v3.1.1
• v3.1.2
• v3.1.4
• v3.1.5
• v3.1.6
• v3.1.7
• v3.1.8
• v3.dev

Build # 2139

Build Type

push

travis-ci

Committed by ben-manes

Commit Message

Don't refresh automatically when waiting for a slow reload (fixed #175)

If the load time exceeded the refreshAfterWrite time then a new refresh
is triggered and the previous was ignored. This was due to how the write
timestamp is used, which was set to the current time to delay expiration
and refresh. When the refresh completes it CAS's to the new value only if
no other writes occurred (so as to not stomp explicit writes and reload a
stale read). The slow reload meant that only the last refresh would be
honored, which may not occur for a long time on a busy system.

This also removes a sync vs async difference that I never remembered why
it was in place. Async didn't have this problem due to the timestamp being
pushed out into the distant future. Since I didn't recall why these were
special cased I had kept them as is, hoping the previous me was smarter
than the current. Seems both were pretty dumb.

Run Details

5716 of 6070 relevant lines covered (94.17%)

0.94 hits per line