Memory-Only Peering: TLS Certificates and Metadata#3307
Memory-Only Peering: TLS Certificates and Metadata#3307KPrasch merged 18 commits intonucypher:v7.2.xfrom
Conversation
639b1eb to
02b5b99
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## v7.2.x #3307 +/- ##
=========================================
Coverage ? 82.70%
=========================================
Files ? 117
Lines ? 11058
Branches ? 0
=========================================
Hits ? 9145
Misses ? 1913
Partials ? 0
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
46962cb to
7241ddf
Compare
KPrasch
left a comment
There was a problem hiding this comment.
I expanded the scope of this PR just slightly to include a full deprecation of the NodeStorage internal API. Going forward peering will be fully managed by FleetSensor and FleetState APIs, as they have their own in-memory storage mechanisms.
| cache.set(address, MOCK_CERT) | ||
| assert not cache.is_expired(address) | ||
| # Wait for the cert to expire | ||
| time.sleep(2) |
There was a problem hiding this comment.
Instead of actually sleeping you can patch time.time() to return a time 2 seconds in the future.
There was a problem hiding this comment.
True. Do you mind If I address this test optimization in PR #3382 in order to avoid more rebases?
|
Thanks everyone! |
Type of PR:
Rework
Required reviews:
2
Issues