muji
muji
Created an issue to learn more about this inconsistency, see: https://github.com/ZenGo-X/multi-party-ecdsa/issues/178
This should now be possible after the recent CGGMP protocol upgrade.
@Montoya, is it possible to take a look at this please?
Huh, of course it's the filesystem version's that differ forcing git's config `core.eol` to `lf` and disabling `core.autocrlf` fixes the issue. I noticed too that changing comments in the migrations...
Hey @jxs, I think this is fairly straightforward to do in a backwards compatible manner, we add a new `migrate_with_options()` function and then the current behavior would call the new...
@archiewood thanks for the info. So that was changed as it used to work fine. In fact it was required for me to use the xl variant with more cores...
I don't think this stale, the problem persists as far as I know.
@yyichenn, I just hit this. Would have been better to update the readme after the release tag has been pushed. Seems strange to document an unreleased release.
It's been a while, would be great to see this land in a new release please 👍 Using `patch.crates-io` for now.