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

Make DownstreamTiming a struct, instead of a class #36473

Merged
merged 1 commit into from
Oct 7, 2024

Conversation

ThomasHabets
Copy link
Contributor

Commit Message: Make DownstreamTiming a struct, instead of a class
Additional Description:This makes it consistent with UpstreamTiming, and makes it easier to dependency inject timing info for testing.
Risk Level: WCPGW
Testing: None
Docs Changes: None
Release Notes: None
Platform Specific Features: None

Copy link

Hi @ThomasHabets, welcome and thank you for your contribution.

We will try to review your Pull Request as quickly as possible.

In the meantime, please take a look at the contribution guidelines if you have not done so already.

🐱

Caused by: #36473 was opened by ThomasHabets.

see: more, trace.

This makes it consistent with UpstreamTiming, and makes it easier to
dependency inject timing info for testing.

Signed-off-by: Thomas Habets <habets@google.com>
@RyanTheOptimist RyanTheOptimist merged commit 563ec60 into envoyproxy:main Oct 7, 2024
19 of 20 checks passed
anitabyte pushed a commit to anitabyte/envoy that referenced this pull request Oct 9, 2024
Commit Message: Make DownstreamTiming a struct, instead of a class
Additional Description:This makes it consistent with UpstreamTiming, and
makes it easier to dependency inject timing info for testing.
Risk Level: WCPGW
Testing: None
Docs Changes: None
Release Notes: None
Platform Specific Features: None

Signed-off-by: Thomas Habets <habets@google.com>
Signed-off-by: anitabyte <anita@anitabyte.xyz>
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.

2 participants