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

[exporterhelper] Deprecate TimeoutSettings, use TimeoutConfig instead #9391

Closed

Conversation

atoulme
Copy link
Contributor

@atoulme atoulme commented Jan 25, 2024

Description:
Deprecate TimeoutSettings, use TimeoutConfig instead

Link to tracking Issue:
#6767

Copy link

codecov bot commented Jan 25, 2024

Codecov Report

Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (6b3b181) 90.23% compared to head (748678c) 90.19%.
Report is 2 commits behind head on main.

Files Patch % Lines
exporter/exporterhelper/common.go 83.33% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #9391      +/-   ##
==========================================
- Coverage   90.23%   90.19%   -0.05%     
==========================================
  Files         345      345              
  Lines       18017    18025       +8     
==========================================
  Hits        16257    16257              
- Misses       1431     1439       +8     
  Partials      329      329              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@atoulme atoulme force-pushed the timeoutsettings_timeoutconfig branch from 3384725 to a158f6e Compare January 25, 2024 08:11
@atoulme atoulme force-pushed the timeoutsettings_timeoutconfig branch from a158f6e to 9b400ab Compare January 25, 2024 08:34
@dmitryax
Copy link
Member

Same as with #9393. I think there is no need to break the existing option for a function that will be replaced with another one

@atoulme
Copy link
Contributor Author

atoulme commented Jan 26, 2024

Going to close for now, and we can always reopen if plans change.

@atoulme atoulme closed this Jan 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants