-
Notifications
You must be signed in to change notification settings - Fork 555
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
Key Update Crash on Allocation Failure #4447
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4447 +/- ##
==========================================
- Coverage 87.30% 86.94% -0.36%
==========================================
Files 56 56
Lines 17630 17630
==========================================
- Hits 15391 15328 -63
- Misses 2239 2302 +63 ☔ View full report in Codecov by Sentry. |
|
||
PacketBuffer.push_back(Header.HeaderByte); | ||
PacketBuffer.insert(PacketBuffer.end(), DestCid.begin(), DestCid.end()); | ||
PacketBuffer.push_back((uint8_t) (PacketNumber >> 24));// TODO - different packet number sizes |
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.
nit: Should the todo be addressed now?
Description
While running spinquic locally I hit a crash in the keyupdate scenario where write key failed to allocate and was later tried to be read. This accounts for that edge case now.
Testing
Covered by spinquic. Also added a QuicDrill test.
Documentation
N/A