Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
sweeper: compute now after the values have been fetched
See commit 040c86b Motivation: 04 Jun 2019 08:05:31 () [] Problem with retrieval of pool data for dmsdca19-1: java.lang.RuntimeException: repository last access time for 0000A91499AE627F4ED0A250CD21A7540793 is later than current system time! - now 1559653531347, last access 1559653531374; this is a bug. It would seem the flaw in the procedure rests in the mtime of the file being updated after now has been computed. This is suggested, in fact, by the billing activity for the above example. Modification: Use system.currentTimeMillis() as the value recomputed just after each file lifetime has been fetched. Result: The negative skew error should not occur (but we have left the check in place just in case). Target: master Request: 5.1 Request: 5.0 Request: 4.2 Acked-by: Dmitry
- Loading branch information