Skip to content

Fixing header parsing bug #1260

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

Merged
merged 2 commits into from
Oct 11, 2022
Merged

Fixing header parsing bug #1260

merged 2 commits into from
Oct 11, 2022

Conversation

stebet
Copy link
Contributor

@stebet stebet commented Oct 10, 2022

Proposed Changes

Headers are not currently parsed correctly, and I'm not sure how long it has been broken. I've added a test that passes now to make sure this doesn't break again.

Types of Changes

  • Bug fix (non-breaking change which fixes issue #NNNN)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause an observable behavior change in existing systems)
  • Documentation improvements (corrections, new content, etc)
  • Cosmetic change (whitespace, formatting, etc)

Checklist

  • I have read the CONTRIBUTING.md document
  • I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
  • All tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in related repositories

Further Comments

@stebet stebet requested a review from michaelklishin October 10, 2022 12:01
michaelklishin
michaelklishin previously approved these changes Oct 10, 2022
@stebet
Copy link
Contributor Author

stebet commented Oct 10, 2022

Mind giving this another review @michaelklishin. I fixed a linting error.

@michaelklishin michaelklishin merged commit 9f29079 into rabbitmq:main Oct 11, 2022
@michaelklishin
Copy link
Contributor

Thank you! This definitely needs backporting.

@bollhals
Copy link
Contributor

This was introduced by #1096 which did not target 6.x, so I don't think we need to backport it.

@stebet
Copy link
Contributor Author

stebet commented Oct 13, 2022

This was introduced by #1096 which did not target 6.x, so I don't think we need to backport it.

Yep, see here: https://github.com/rabbitmq/rabbitmq-dotnet-client/pull/1096/files#r994516089. Sneaky bug, all due to one missing .Slice

@lukebakken lukebakken deleted the headerfix branch June 3, 2024 17:49
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