- πΊπΈUnited States moshe weitzman Boston, MA
Looks to me like this is done in latest version.
The module currently relies upon the time() function to track when various caches are cleared. The time() function tracks events to the nearest second. The problem is that there can be thousands of operations within an individual second, so a second becomes an extremely imprecise value to work from. The current system leads to issues like #2444221: cache_lifetime should not affect cache_clear_all() β , whereby it's impossible to discern between cache_set() being called before or after a cache_clear_all().
Change all time-based logic to use microtime() instead of time().
Write a patch, test it.
None.
None.
Additional variables are kept to track the microtime of various events in addition to the timestamp.
Needs review
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Looks to me like this is done in latest version.