afonso/core-extra
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

updated usage of time.time to time.monotonic or time.perf_counter due to time.time possibly rolling backwards

Browse source
This commit is contained in:
Blake Harnden 2019-12-06 09:42:41 -08:00
parent b9bbf397c9
commit 45a23a6c14
11 changed files with 29 additions and 29 deletions
Download patch file Download diff file Expand all files Collapse all files

8
daemon/core/nodes/network.py
View file

@ -57,7 +57,7 @@ class EbtablesQueue:
:return: nothing
"""
with self.updatelock:
self.last_update_time[wlan] = time.time()
self.last_update_time[wlan] = time.monotonic()
if self.doupdateloop:
return
@ -108,9 +108,9 @@ class EbtablesQueue:
:rtype: float
"""
try:
elapsed = time.time() - self.last_update_time[wlan]
elapsed = time.monotonic() - self.last_update_time[wlan]
except KeyError:
self.last_update_time[wlan] = time.time()
self.last_update_time[wlan] = time.monotonic()
elapsed = 0.0
return elapsed
@ -122,7 +122,7 @@ class EbtablesQueue:
:param wlan: wlan entity
:return: nothing
"""
self.last_update_time[wlan] = time.time()
self.last_update_time[wlan] = time.monotonic()
self.updates.remove(wlan)
def updateloop(self):