-
-
Notifications
You must be signed in to change notification settings - Fork 440
[interceptor] control max packet age for NACK responses #313
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
Conversation
5612d59 to
8c869b4
Compare
e22f3a4 to
5572970
Compare
Codecov Report
Base: 59.87% // Head: 59.87% // No change to project coverage 👍
Coverage data is based on head (
3e47da6) compared to base (3e47da6).
Patch has no changes to coverable lines.
❗ Current head 3e47da6 differs from pull request most recent head 5302015. Consider uploading reports for the commit 5302015 to get more accurate results
Additional details and impacted files
@@ Coverage Diff @@ ## master #313 +/- ## ======================================= Coverage 59.87% 59.87% ======================================= Files 503 503 Lines 47644 47644 Branches 12357 12357 ======================================= Hits 28528 28528 Misses 9889 9889 Partials 9227 9227
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.
☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.
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.
👍
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.
5572970 to
5302015
Compare
juancampa
commented
Feb 8, 2023
@k0nserv any plan on merging this any time soon? I think we're also hitting the edge case of retransmissions aggravating the problem
juancampa
commented
Feb 8, 2023
I also wonder how receivers handle the case where certain nacks are ignored. E.g. I've seen Chrome sending the same nack over and over.
@k0nserv anything left to do here except (a) rebase (b) fix conflicts ? thanks 🙏
I don't believe so
c2f4c33 to
fb59f4b
Compare
5402eaf to
ffead9f
Compare
463d5f6 to
a1f8f19
Compare
Uh oh!
There was an error while loading. Please reload this page.
TODO: