Open sigaloid opened 1 year ago
Confirmed that this fixes the issue (and stats appear to be unchanged).
I am still getting a ‘no entry found for key’ panic with d56a597.
What version of valgrind are you on? And is it pointing to my fork in your Cargo.toml?
Strange that it still wouldn't work, as that's the only cause :(
What version of valgrind are you on? And is it pointing to my fork in your Cargo.toml?
3.21.0, and yes, I removed Cargo.lock to make sure it was picking it up, and it still panics.
I can confirm the problem noticed by @bluebear94, I still get the error. Also, I found the following in the cargo output, verifying that this PR is used:
Compiling iai v0.1.1 (https://github.com/sigaloid/iai?rev=d56a597#d56a5971)
I needed a cargo update
but afterwards it worked with iai = { git = "https://github.com/sigaloid/iai", rev = "d56a597" }
.
@sigaloid: I am relying on your bugfix in the HDT library on crates.io but depending on a GitHub repository is making me nervous. As the main developer of this project, @bheisler has been inactive for the last 2 and a half years and I could not find any contact information, it seems to me as if this won't get merged in the near future. Could you consider publishing your fork on crates.io, so other crates can reliably depend on a fixed version of iai?
Fixes #34.
If you want to use this before it gets merged, replace your
iai
line inCargo.toml
to this: