You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Certain permutations of a valid Cargo.lock, which can happen in large codebases, will result in a version mismatch where tls-listener uses a different version of tokio-rustls than zenoh-link-tls does.
Describe the bug
Certain permutations of a valid Cargo.lock, which can happen in large codebases, will result in a version mismatch where tls-listener uses a different version of
tokio-rustls
thanzenoh-link-tls
does.I think this is possible because tls-listener can use either v0.25.0 or v0.26.0, whereas
zenoh-link-tls
only ever uses v0.26.0.Instead, zenoh-link-tls should use the version that tls-listener exports
To reproduce
I have created a minimal reproducible Cargo.lock and full example here: TheButlah/bugs#2
Here are the crates and how they depend on tokio-rustls:
System info
The text was updated successfully, but these errors were encountered: