After #349, Windows still sometimes has a scan timeout due to getNow inaccuracy between nodes. This reverts the scan timestamps to use time.time(). Because the scan check now accepts an equal timestamp as satisfying the scan request, the inaccuracy of time.time() shouldn't be a problem in this case.
After #349, Windows still sometimes has a scan timeout due to
getNowinaccuracy between nodes. This reverts the scan timestamps to usetime.time(). Because the scan check now accepts an equal timestamp as satisfying the scan request, the inaccuracy oftime.time()shouldn't be a problem in this case.