Version
0.4.0
Environment
linux, 3.13
Expected behavior
Had to migrate a bunch of legacy wallets from 1.1.33 to keria:0.4.0/keripy:1.2.13. Ran into #257 . Didn't notice at first that the fix from that issue was the "fix-sigs" command. Thought the kli migrate would fix the issue but then found that the command was referenced as the fix for that issue.
Tried to run the command and realized it wasn't doing anything after some debugging.
sig-fix should run with output (or at least print starting/stopping/failing) behavior.
Actual behavior
sig-fix exits (successfully 0 return) with no output to console and doesn't seem to run at all (based on some lite debugging). (Also doesn't fix the issue referenced in #257)
Steps to reproduce
Run the command on some wallets produced previously to 1.2.0 as in the referenced issue #257.
Version
0.4.0
Environment
linux, 3.13
Expected behavior
Had to migrate a bunch of legacy wallets from 1.1.33 to keria:0.4.0/keripy:1.2.13. Ran into #257 . Didn't notice at first that the fix from that issue was the "fix-sigs" command. Thought the
kli migratewould fix the issue but then found that the command was referenced as the fix for that issue.Tried to run the command and realized it wasn't doing anything after some debugging.
sig-fix should run with output (or at least print starting/stopping/failing) behavior.
Actual behavior
sig-fix exits (successfully
0return) with no output to console and doesn't seem to run at all (based on some lite debugging). (Also doesn't fix the issue referenced in #257)Steps to reproduce
Run the command on some wallets produced previously to 1.2.0 as in the referenced issue #257.