Skip to content

fix: error raised for env checks in LogLimits and SpanLimits #4458

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 3 commits into from
Mar 3, 2025

Conversation

jomcgi
Copy link
Contributor

@jomcgi jomcgi commented Mar 1, 2025

Description

Current implementation raises a value error trying to create the error message.
Updated error message format to use positional instead of named params.
Added test cases to validate the correct errors are raised.

Fixes #4456

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

  • Added test cases & ran locally with tox

Does This PR Require a Contrib Repo Change?

  • No.

Checklist:

  • Followed the style guidelines of this project
  • Changelogs have been updated
  • Unit tests have been added
  • Documentation has been updated

Sorry, something went wrong.

@jomcgi jomcgi force-pushed the fix-error-message-format branch 4 times, most recently from da96f65 to 1a795b2 Compare March 1, 2025 12:37
@jomcgi jomcgi changed the title [WIP] fix: error raised for env checks in LogLimits and SpanLimits fix: error raised for env checks in LogLimits and SpanLimits Mar 1, 2025
@jomcgi jomcgi marked this pull request as ready for review March 1, 2025 12:46
@jomcgi jomcgi requested a review from a team as a code owner March 1, 2025 12:46
@jomcgi jomcgi force-pushed the fix-error-message-format branch 2 times, most recently from 91109ed to 94f10ba Compare March 1, 2025 13:27

Verified

This commit was signed with the committer’s verified signature.
liggitt Jordan Liggitt
Current implementation raises a value error trying to create the error message.
Updated error message format to use positional instead of named params.
Added test cases to validate the correct errors are raised.
@jomcgi jomcgi force-pushed the fix-error-message-format branch from 94f10ba to d31d1cc Compare March 1, 2025 15:21
xrmx added 2 commits March 1, 2025 19:34

Verified

This commit was signed with the committer’s verified signature. The key has expired.
ying-jeanne Ying WANG
@xrmx xrmx enabled auto-merge (squash) March 3, 2025 14:59
@xrmx xrmx merged commit afec2dd into open-telemetry:main Mar 3, 2025
384 checks passed
@jomcgi jomcgi deleted the fix-error-message-format branch March 3, 2025 19:05
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.

ValueError when initializing Tracer
2 participants