Skip to content

inprocess: Support tracing message sizes guarded by flag #11629

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 4 commits into from
Oct 23, 2024

Conversation

shivaspeaks
Copy link
Member

No description provided.

@@ -212,6 +215,7 @@ public ServerStreamTracer newServerStreamTracer(String fullMethodName, Metadata

@Before
public void setUp() {
System.setProperty(GRPC_EXPERIMENTAL_SUPPORT_TRACING_MESSAGE_SIZES, "true");
Copy link
Contributor

Choose a reason for hiding this comment

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

You should do this in the specific test, not here which is the setup step for every test. We need to have 2 tests one that sets the property and one that doesn't. The test that does setProperty should have a try - finally block to System.clearProperty in the finally block as well.

Copy link
Member

@ejona86 ejona86 Oct 22, 2024

Choose a reason for hiding this comment

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

Since we would expect to have this flag for ~1 week and we want to get this in quickly (vs the larger revert), I suggest not testing at all with GRPC_EXPERIMENTAL_SUPPORT_TRACING_MESSAGE_SIZES=true (just use the default, whatever it is).

@shivaspeaks
Copy link
Member Author

shivaspeaks commented Oct 22, 2024 via email

@ejona86
Copy link
Member

ejona86 commented Oct 22, 2024

You mean we should move it to somewhere else? Perhaps
to a place where constants are defined?

Add it as a field to the transport.

@shivaspeaks shivaspeaks requested a review from ejona86 October 22, 2024 17:46
@shivaspeaks shivaspeaks merged commit b65cbf5 into grpc:master Oct 23, 2024
14 of 15 checks passed
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 22, 2025
@shivaspeaks shivaspeaks deleted the flag-guard branch May 19, 2025 06:18
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants