-
Notifications
You must be signed in to change notification settings - Fork 292
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
feat: Implement Tox network profiler #1885
base: master
Are you sure you want to change the base?
Conversation
b93009f
to
75fd324
Compare
84ab794
to
687d5b5
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1885 +/- ##
==========================================
- Coverage 72.89% 72.48% -0.42%
==========================================
Files 149 150 +1
Lines 30570 30874 +304
==========================================
+ Hits 22285 22379 +94
- Misses 8285 8495 +210 ☔ View full report in Codecov by Sentry. |
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.
Reviewed 10 of 19 files at r1, 8 of 9 files at r2, all commit messages.
Reviewable status: complete! 1 of 1 approvals obtained (waiting on @JFreegman)
toxcore/tox_private.h, line 60 at r1 (raw file):
Previously, JFreegman wrote…
The reason I named it ZERO is because it has a different purpose depending on the packet type (see the above comment). Any suggestions?
Ok, that's fine then.
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.
Reviewed 1 of 19 files at r1.
Reviewable status: complete! 1 of 1 approvals obtained (waiting on @JFreegman)
9ee9543
to
38aecfd
Compare
8795684
to
f794ffa
Compare
1955d38
to
f785959
Compare
Also fixed u64 formatting in the netprof auto test
I still want to check toxav and custom packets for friend 2 friend. |
What do you want to check? Both use the same net_crypto packet sending functions as everything else and both use the NET_PACKET_CRYPTO_DATA packet ID. Nothing special happens with either one at the packet recording level. It's easy enough to test via Toxic's netprof branch. |
@JFreegman you are correct, I wrongly assumed this made a difference. |
@@ -0,0 +1,121 @@ | |||
/** Auto Tests: basic network profile functionality test (UDP only) | |||
* TODO(JFreegman): test TCP packets as well |
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.
is this todo still relevant?
This change is