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

Stub and server lifecycle fixes #4268

Closed

Conversation

nathanielmanistaatgoogle
Copy link
Member

Fixes at least #3820, #529 and possibly a few other problems too.

For a termination action to properly mark an _End as having stopped it
must clear the _End's _cycle attribute. To be able to do that the
termination action must hold a reference to the _End instance.
Migrating the _termination_action behavior that creates termination
actions into the scope of the _End instance is the best way to afford
the needed instance reference.
Context management is implemented.

Stub deletion now cancels all RPCs immediately.
@nathanielmanistaatgoogle
Copy link
Member Author

Crud, wrong branch!

@lock lock bot locked as resolved and limited conversation to collaborators Jan 29, 2019
@lock lock bot unassigned soltanmm Jan 29, 2019
lidizheng pushed a commit to lidizheng/grpc that referenced this pull request Feb 12, 2021
limiting user defined header alterations to 25 alterations (add/remove request/response headers) and 1024 bytes per alteration.

Risk Level: medium (if someone needs higher limits we can roll back and roll forward with new values)
Testing: new unit tests of one of the 17 fields affected
Release Notes: noted the new limitations
Fixes grpc#4268

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>

Mirrored from https://github.com/envoyproxy/envoy @ b9bee1e649399f838b23cb1cedfba888e1925605
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants