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

v0.8.1 #115

Merged
merged 2 commits into from
Feb 16, 2021
Merged

v0.8.1 #115

merged 2 commits into from
Feb 16, 2021

Conversation

romanb
Copy link
Contributor

@romanb romanb commented Feb 16, 2021

To avoid surprises, it seems best to backport the part of v0.9 that ignores received frames for unknown streams into a v0.8.1 release. Otherwise nodes running v0.8 may react with a stream reset if they get a window update from a node running v0.9 while the stream is already closing. Rolling out v0.8.1 first should avoid such hiccups.

cc @mxinden

Copy link
Member

@tomaka tomaka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't reviewed the logic, but if nobody else reviews I can give you an approval

Copy link
Member

@mxinden mxinden left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To avoid surprises, it seems best to backport the part of v0.9 that ignores received frames for unknown streams into a v0.8.1 release. Otherwise nodes running v0.8 may react with a stream reset if they get a window update from a node running v0.9 while the stream is already closing. Rolling out v0.8.1 first should avoid such hiccups.

Yes, good point! 👍

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.

3 participants