Steven Allen 810b492220 fix: handle funky clocks when removing expired addresses ... When setting the TTL to 0, we expect `UpdateAddrs` to atomically delete the addresses. However, due to funky clock stuff, "now" isn't always consistent and seems to make us think these addresses are _about_ to expire. Funky clock stuff -> `time.Now().Add(0).Unix() > time.Now().Unix()` in some cases...		2021-07-16 20:33:57 -07:00
..
addr_book_gc_test.go	test: use leveldb instead of badger	2021-07-16 19:45:29 -07:00
addr_book_gc.go	chore(dep): update go-log	2020-02-17 11:38:14 -05:00
addr_book.go	fix: handle funky clocks when removing expired addresses	2021-07-16 20:33:57 -07:00
cache.go	add Keys() function to private cache interface for completeness.	2018-11-15 18:39:38 +00:00
cyclic_batch.go	chore: update to latest go error handling	2021-07-16 10:38:00 -07:00
ds_test.go	test: use leveldb instead of badger	2021-07-16 19:45:29 -07:00
keybook.go	Certified addresses (#98)	2020-03-06 12:07:36 +00:00
metadata.go	fix: handle nil peer IDs	2020-04-05 23:05:41 -07:00
peerstore.go	fix: avoid copying locks/waitgroups	2021-07-15 17:16:22 -07:00
protobook.go	changes for the new interface	2020-05-11 13:07:08 +05:30