Fix noisy tracing failure from Rust's global tracing
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 49/100
Research direction
Start by tracing how pact-ruby initializes the Rust tracing subscriber and resets pacts between interactions; the issue does not name specific files or tests. Reproduce the failure by running pact tests repeatedly, including with log_level: :warn, and identify why the process-global subscriber is initialized more than once. Done when repeated interactions no longer emit the initialization error.
Written by the indexing model from the issue text.
Description
Running pact tests repeatedely generates tracing error, per test/interaction.
Failed to initialise global tracing subscriber - a global default trace dispatcher has already been set
I have confirmed they still appear when setting opts { log_level: :warn }. Pact 2.1.2 repeatedly initializes Rust’s process-global tracing subscriber, including when resetting the pact between interactions.
- Dominant language
- Ruby
- Stars
- 2.2k
- Forks
- 220
- Avg merge
- 5h 22m
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from pact-foundation/pact-ruby
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
pact-foundation/pact-ruby#435 ·
-
Dependency DashboardOpen
Difficulty 1/5 Under an hour Newbie friendliness 10/100
pact-foundation/pact-ruby#336 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
pact-foundation/pact-ruby#321 ·
All issues in pact-foundation/pact-ruby
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
riscv/riscv-unified-db#2841 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
OpenAPITools/openapi-generator#25768 ·
Maintainers usually reply within 1 day
-
bug documentation priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
davidteren/mutineer#513 ·
Maintainers usually reply within 2 days
-
API: per_page is bitwise-OR'd with 10, so page sizes are wrongPossibly taken @kzroo claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
TarteelAI/quranic-universal-library#1088 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
olivierlacan/trebuche#8 ·