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

[receiver/dockerstats] remove duplicate Timeout setting #26114

Merged

Conversation

codeboten
Copy link
Contributor

Use the Timeout setting from ScraperHelper instead

Use the Timeout setting from ScraperHelper instead

Signed-off-by: Alex Boten <aboten@lightstep.com>
@codeboten codeboten requested a review from a team as a code owner August 25, 2023 22:13
@codeboten codeboten requested a review from atoulme August 25, 2023 22:13
Signed-off-by: Alex Boten <aboten@lightstep.com>
@crobert-1
Copy link
Member

I filed #26123 to address the CI failure, it's unrelated to this change.

Copy link
Contributor

@jamesmoessis jamesmoessis left a comment

Choose a reason for hiding this comment

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

Nice, makes it easy that the scraperhelper timeout has the same signature.

# Use this changelog template to create an entry for release notes.

# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
change_type: breaking
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this really a breaking change if there is no impact to users? Seems to be an enhancement to me.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's a breaking change for the API if anyone was instantiating the configuration for the component programmatically

@codeboten codeboten merged commit 7f452e5 into open-telemetry:main Aug 30, 2023
93 checks passed
@github-actions github-actions bot added this to the next release milestone Aug 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants