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
The issue comes from different versions of the secp256k1 library being used due to dependency conflicts. This problem occurs specifically with mutants, as they copy the project to a temporary folder and build it there, causing issues with binding to one of the secp256k1 versions.
https://mutants.rs/in-place.html
The simplest fix is to build mutants within the same project instead of copying it elsewhere. This works fine in CI environments since the project state doesn’t need to be preserved after the run. However, for local development, it’s better to run mutants on a copy of the project, as they modify files.
^ The latest versions for stacks-common, clarity-vm and stacks-codec are the ones displayed above. So without a new release on all of them, there will continue to be multiple versions of secp256k1.
TLDR
The issue comes from different versions of the secp256k1 library being used due to dependency conflicts. This problem occurs specifically with mutants, as they copy the project to a temporary folder and build it there, causing issues with binding to one of the secp256k1 versions.
Conflicting dependencies:
Solution
https://mutants.rs/in-place.html
The simplest fix is to build mutants within the same project instead of copying it elsewhere. This works fine in CI environments since the project state doesn’t need to be preserved after the run. However, for local development, it’s better to run mutants on a copy of the project, as they modify files.
More details
^ The latest versions for stacks-common, clarity-vm and stacks-codec are the ones displayed above. So without a new release on all of them, there will continue to be multiple versions of
secp256k1
.The text was updated successfully, but these errors were encountered: