Skip to content
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

don't enqueue stream when receiving reordered MAX_STREAM_DATA frames #4269

Merged

Conversation

marten-seemann
Copy link
Member

Minor optimization. Not sure it matters at all, but it seemed easy enough.

Copy link

codecov bot commented Jan 25, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (baeec0f) 84.09% compared to head (c453127) 84.10%.
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #4269      +/-   ##
==========================================
+ Coverage   84.09%   84.10%   +0.02%     
==========================================
  Files         150      150              
  Lines       15421    15425       +4     
==========================================
+ Hits        12967    12973       +6     
+ Misses       1952     1950       -2     
  Partials      502      502              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@marten-seemann marten-seemann changed the title don't enqueue stream for sending on reordered MAX_STREAM_DATA frames don't enqueue stream when receiving reordered MAX_STREAM_DATA frames Jan 25, 2024
@marten-seemann marten-seemann added this to the v0.42 milestone Feb 3, 2024
@marten-seemann marten-seemann merged commit 198de32 into master Feb 3, 2024
34 checks passed
@marten-seemann marten-seemann deleted the dont-queue-stream-on-reordered-max-stream-data branch February 8, 2024 02:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants