-
Notifications
You must be signed in to change notification settings - Fork 5.1k
use new buffers by default #7883
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
Conversation
@securityinsanity sure, the code looks good to me, however I'm not merging this until the security release, to keep the upgrade process smooth. |
👍 I agree there, our pipeline just checks for approved PRs before picking. Thanks! |
I believe we should be good to merge this now, since 1.11.1 is fully out? |
🤞 please merge master. /wait |
Can do here in a bit. |
fixes envoyproxy#7314 this commit changes the default implementation of buffers to the new implementation by default. Signed-off-by: Cynthia Coan <ccoan@instructure.com>
Master has been merged, successfully 👍 . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Description:
switch Envoy::Buffer to Brian Pane's implementation (aka "new buffers") by default.
Risk Level: Medium
Testing:
Ran through the following test plan locally:
There's also be some testers in actual environments see #7314 , and Envoy Meeting Minutes.
Docs Changes: None
Release Notes: Added a line about how it's the default, including how to turn it off.
fixes #7314