The reason why the CI of tlv-tool started failing lately is because there is a new check in latest log which checks if there are multiple, incompatible log-max-levels which are specified as features.
And we do have incompatibility:
In rs-matter:
log = { version = "0.4", features = ["max_level_debug", "release_max_level_debug"] }
(This is since forever, i.e. since before I was around.)
In tlv-tool:
log = {version = "0.4.14", features = ["max_level_trace", "release_max_level_warn"]}
This PR simply removes the custom levels from tlv-tool and tlv-tool will use the ones from rs-matter (which might have been the case anyway before - silently).
The reason why the CI of tlv-tool started failing lately is because there is a new check in latest
logwhich checks if there are multiple, incompatible log-max-levels which are specified as features.And we do have incompatibility:
In
rs-matter:(This is since forever, i.e. since before I was around.)
In tlv-tool:
This PR simply removes the custom levels from tlv-tool and tlv-tool will use the ones from
rs-matter(which might have been the case anyway before - silently).Open to other suggestions.