Fix noisy tracing failure from Rust's global tracing

Open
#437 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
49/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
ruby
Domain
testing

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pact-foundation/pact-ruby

All issues in pact-foundation/pact-ruby

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.