rust_kvs's json_backend.rs fails to compile against score_log's current ScoreDebug trait because Path/&Path has no ScoreDebug impl, while debug!/error! log macros require it for {:?} arguments.
Error (representative, E0277, 21 occurrences total):
error[E0277]: the trait bound Path: ScoreDebug is not satisfied
--> src/rust/rust_kvs/src/json_backend.rs:342:9
|
342 | debug!("Saving KVS file: {:?}", kvs_path);
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait ScoreDebug is not implemented for Path
= note: required for &Path to implement ScoreDebug
note: required by a bound in score_log::score_log_fmt::Placeholder::<'a>::new
Also hits lines 344, 348-351, 354 in the same file (all kvs_path/hash_path logging calls).
Impact:
Downstream, reference_integration's full Rust FIT target (rust_test_scenarios, which depends on rust_kvs) cannot build. We worked around it by splitting a rust_lifecycle_test_scenarios target that avoids the rust_kvs/orchestrator dependency chain entirely (see feature_integration_tests/test_scenarios/rust/BUILD:36-62), but this is a stopgap — the workaround target should be removable once this is fixed.
rust_kvs's json_backend.rs fails to compile against score_log's current ScoreDebug trait because Path/&Path has no ScoreDebug impl, while debug!/error! log macros require it for {:?} arguments.
Error (representative, E0277, 21 occurrences total):
error[E0277]: the trait bound
Path: ScoreDebugis not satisfied--> src/rust/rust_kvs/src/json_backend.rs:342:9
|
342 | debug!("Saving KVS file: {:?}", kvs_path);
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait
ScoreDebugis not implemented forPath= note: required for
&Pathto implementScoreDebugnote: required by a bound in
score_log::score_log_fmt::Placeholder::<'a>::newAlso hits lines 344, 348-351, 354 in the same file (all kvs_path/hash_path logging calls).
Impact:
Downstream, reference_integration's full Rust FIT target (rust_test_scenarios, which depends on rust_kvs) cannot build. We worked around it by splitting a rust_lifecycle_test_scenarios target that avoids the rust_kvs/orchestrator dependency chain entirely (see feature_integration_tests/test_scenarios/rust/BUILD:36-62), but this is a stopgap — the workaround target should be removable once this is fixed.