On Windows, time.time() has a low resolution (~16ms), so objects created in sequence sometimes have the same 'created' timestamp.
Creation time is now computed by adding the precise time elapsed since node startup (from time.perf_counter) to the recorded unix time at node startup, in the new helper timeUtil.getNow().
On Windows,
time.time()has a low resolution (~16ms), so objects created in sequence sometimes have the same 'created' timestamp.Creation time is now computed by adding the precise time elapsed since node startup (from
time.perf_counter) to the recorded unix time at node startup, in the new helpertimeUtil.getNow().Fixes #344