open-telemetry / open-telemetry/opentelemetry-ruby
Ensure all methods of any instrument are safe to be called concurrently
Open
Nobody has claimed this yet.
keep
metrics
- Dominant language
- Ruby
- Stars
- 606
- Forks
- 301
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 42
Description
All methods of an instrument must be safe to be called concurrently. This might be the case already, but we should verify that it is. If the methods are not safe to be called concurrently, update the code.
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 locating the Ruby instrument implementations and their existing tests, then compare every public method with the OpenTelemetry metrics API concurrency requirement. Verify concurrent calls across all instrument types; done means the methods are demonstrably safe, with tests covering the requirement and code changes where safety is missing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100