Closed behnam closed 6 years ago
Could it be an issue with flame
changing transitive dependencies?
Hum... not sure what you mean by transitive dependencies.
I'm looking at git diff 590014d e1cf412
and can't find anything suspicious.
@behnam I mean, could adding flame as a dependency change the versions of other dependencies in your project?
@behnam: any update on this? I don't think that this is the fault of bincode.
No updates here, @TyOverby . I guess it's a version conflict for serde_derive stuff, but I don't find it.
If this still repros for you, could you send me the contents of your Cargo.lock file before and after?
Also try building flame
with and without the json
feature enabled.
Thanks, @TyOverby. Here are the files:
Also, I disabled default flame
features, but still got the same error.
your before/after cargo.lock.toml files are identical
Closing due to inactivity; please reopen if this is still an issue.
As the
0.1.12
update yesterday, I noticed that building lib unit tests is failing inunicode-bidi
withflame_it
feature. I went back and minimized the changes for the break, which actually reduced to onlyextern crate flame;
, and only happening for=0.1.12
.Here's the commit causing error on a stable
unicode-bidi
build: https://github.com/behnam/rust-unicode-bidi/commit/6e6fc7890bca1e1fe952e69508dba9369e1d37b1Here's the error:
from https://travis-ci.org/behnam/rust-unicode-bidi/jobs/243806493#L259
I have no idea how flame can cause this in a module that doesn't use any of the traits. What do you think, @TyOverby ?