Skip to content

Conversation

@HoneyryderChuck
Copy link
Collaborator

Contains fixes for some string encoding issues reported here and here.

Releases a new patch version (1.1.1)

…acking and prepending the frame header

certain DATA payload inputs were keeping the original encoding right before prepending the binary header, which could generate an incompatible encoding error

Fixes HoneyryderChuck/httpx#83
lib users will store the ping data input to compare when receiving the peer PING frame, so it may be surprising if the data does not match because the mutable arg was changed
calls to #event already transition @State to the next state, so this is redundant
remove all calls to "#process_priority" inside "#transition", as
it  should only handle state machine transitions. besides, #receive
already does that type of frame processing calls before calling
"#transition" .

this also corrects stream state management when it comes to taking
priority frames into account when sending, as per the documentation
on each state block, which explicitly states the cases which were not
being handled.
Copy link
Collaborator

@mullermp mullermp left a comment

Choose a reason for hiding this comment

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

Seems fine - I can do a sanity test with the SDK later this week.

@HoneyryderChuck
Copy link
Collaborator Author

thx. I'll be issuing a release today though, as this was disruptive to some folks who upgraded the lib, and I'd expect more to come as time passes by. I already ran a few sanity checks on my side as well, and the original issue reporters have already deployed the patch and confirmed it fixes the issue.

@HoneyryderChuck HoneyryderChuck merged commit 82922e4 into main Apr 16, 2025
10 checks passed
@HoneyryderChuck HoneyryderChuck deleted the buffer-encoding-issues branch April 16, 2025 00:03
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