open-telemetry / open-telemetry/opentelemetry-python
Raise Failure or Timeout in tracing and logs
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
Make sure tracing and logs functions that have to raise a Failure or Timeout exception do so.
Originally posted by @srikanthccv in https://github.com/open-telemetry/opentelemetry-python/pull/2599#discussion_r849585141
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the tracing and logging functions related to Failure and Timeout handling, then read the discussion referenced from pull request #2599. Identify which functions are expected to raise these exceptions and verify their current behavior. Done means the applicable functions raise Failure or Timeout as required, with tests covering the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100