open-telemetry / open-telemetry/opentelemetry-java-instrumentation
What to do when muzzle mismatches occur?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.6k
- Forks
- 1.2k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 228
Description
A muzzle mismatch isn't really a bad thing. It just shows that instrumentation can't be applied and this is what it is for. Currently we add preconditions to instrumentations when muzzle fails when cross testing. Wondering whether we should bother with this at all.
Originally posted by @laurit in https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/17306#issuecomment-4167902867
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 reading the muzzle cross-testing setup and the current instrumentation preconditions mentioned in the issue. Compare how mismatch cases are handled today and use the linked discussion to understand the competing options. Done means reaching and documenting a clear project decision about whether these preconditions are needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100