Closed bioinformatist closed 1 year ago
Actually we don't have v0.5.3 tikv-jemallocator, instead we only have 0.5.3 tikv-jemalloc-sys. If you have Cargo.lock checked in the version control, it's possible an old version is used. You can update it by cargo update -p tikv-jemalloc-sys
.
Yes, it did solve the problem. Thank you for your reply~
Hey bro, I'v used
tikv-jemallocator
v0.5.0 for custom allocator in our projects for a long time.The
cargo clippy
bring me notes below these days:I noticed that since v0.5.3
tikv-jemallocator
do not depend onfs_extra
at all, but this version seems failed published on https://crates.io.Is there something wrong with CI? Would you mind fix this problem? Thanks in advance.