0.4.20 pactffi_mock_server_logs empty - mismatch in tracing library

pactffi_mock_server_logs are empty, in 0.4.20 release.

Initially identified in pact-net's test suite when attempting to update to libpact_ffi 0.4.20. pact-net uses pactffi_log_to_buffer when it initialises, and has a test to check that pactffi_mock_server_logs actually returns logs (and it failed)

Cause

I believe this is due to a mis-match in the logging libraries in pact_models, compared to the rest of the pact rust estate

tracing-0.1.37 https://github.com/pact-foundation/pact-reference/blob/master/rust/pact_models/Cargo.toml#L48
tracing-subscriber-0.3.16 https://github.com/pact-foundation/pact-reference/blob/5699cab757e31875b74ea8ce98cd9821dc331421/rust/pact_models/Cargo.toml#L67C1-L67C93

All other crates

Reproductions

Added a test, which requires a buffer log sink. I believe the full test run sets a different global sink, so the test is ignored in the main run, and executed in isolation. It's not terribly pretty but it does the job.

✅ tag libpact_ffi-v0.4.19

❌ tag libpact_ffi-v0.4.20

Resolution

Suggest

Update pact_models to match tracing libs
1. Requires consuming in pact-plugin-driver & pact-core-mock-server
Pin logging libs explicitly with version="=x.y.z", note the = sign in the version number. This forces pinned resolution

Testing

Update pact_models to same logging libs
Update pact_mock_server to use updated pact_models
Update pact-plugin-driver, as it consumes pact_models, and are depended on by pact_mock_server
Update all the things in pact-ref to point to updated pact_mock_server and pact-plugin-driver

pact-plugin-driver

Delta https://github.com/pact-foundation/pact-plugins/compare/main...YOU54F:pact-plugins:fix/logging_min?expand=1
Passing Run https://github.com/YOU54F/pact-plugins/actions/runs/9423940849/job/25963273163 (failures due to no token to publish to PactFlow)

pact-foundation / pact-reference