-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changed to new socket interface from network library. #266
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #266 +/- ##
==========================================
+ Coverage 64.94% 65.32% +0.37%
==========================================
Files 48 48
Lines 5263 5188 -75
==========================================
- Hits 3418 3389 -29
+ Misses 1845 1799 -46
☔ View full report in Codecov by Sentry. |
de56f4b
to
56e67d2
Compare
8c0318e
to
b127816
Compare
b127816
to
b6b738c
Compare
.await | ||
.unwrap() | ||
.unwrap_or(local_clock.now()); | ||
.unwrap(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so a missing timestamp is a panic now? and not even a nice panic but an unwrap on a (from the user) arbitrary line?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this either needs some sort of comment for why unwrapping is OK, or something like an expect or custom panic with more information on what went wrong
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is dealt with in the follow up pull request.
No description provided.