Cache and "refresh" behavior not clear

Open
#36 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
kotlin
Domain
documentation

Research direction

Start by tracing the cacheExpirationMs and minWaitTimeBetweenSyncMs handling around getCurrentTime(). Verify the minute-3 scenario, then document the resulting behavior and update the relevant documentation or usage guidance; the issue does not name a file or test to run.

Written by the indexing model from the issue text.

Description

If the cacheExpirationMs is 1 minute and minWaitTimeBetweenSyncMs is 5 minutes, what will happen when I do a getCurrentTime() at minute 3? Will the value in the cache be used even though it is expired, will a sync be forced even though it still has 2 minutes left or will it just use the local device time?

Dominant language
Kotlin
Stars
287
Forks
17
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lyft/Kronos-Android

All issues in lyft/Kronos-Android

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.