mirror of
https://github.com/facebookincubator/mvfst.git
synced 2025-07-29 03:41:11 +03:00
Do not add ack frames to packet when it was rebuilt in cloning scheduler
Summary: We may end up writing acks after a length-less stream frame and it will be considered garbage data by the peer. The acks will be written later as usual, outside of cloning scheduler. Reviewed By: mjoras Differential Revision: D35561912 fbshipit-source-id: 9334523b984870fa525c856a504ae7d2ae4f34c3
This commit is contained in:
committed by
Facebook GitHub Bot
parent
2f4b66bb64
commit
d31df23ca5
@ -792,7 +792,7 @@ TEST_F(QuicPacketSchedulerTest, CloneSchedulerHasHandshakeDataAndAcks) {
|
||||
EXPECT_TRUE(result.packetEvent.has_value());
|
||||
EXPECT_TRUE(result.packet.has_value());
|
||||
|
||||
// Cloned packet has to have at least one ack frame AND the crypto data.
|
||||
// Cloned packet has to have crypto data and no acks.
|
||||
bool hasAckFrame = false;
|
||||
bool hasCryptoFrame = false;
|
||||
for (auto iter = result.packet->packet.frames.cbegin();
|
||||
@ -810,7 +810,7 @@ TEST_F(QuicPacketSchedulerTest, CloneSchedulerHasHandshakeDataAndAcks) {
|
||||
break;
|
||||
}
|
||||
}
|
||||
EXPECT_TRUE(hasAckFrame);
|
||||
EXPECT_FALSE(hasAckFrame);
|
||||
EXPECT_TRUE(hasCryptoFrame);
|
||||
}
|
||||
|
||||
|
Reference in New Issue
Block a user