This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
generator command not enabling block generation #7783
Comments
shuse2
changed the title
shuse2
added a commit
that referenced
this issue
Dec 10, 2022
### What was the problem? This PR resolves #7783 ### How was it solved? - Revert generator enable/disable command to have `--use-status-value` - Move height/max-height-generated/max-height-prevoted as flag - Revert temporally lisk-db version to the previous version because it leaves locks value LiskArchive/lisk-db#78 - Fix to pass `keypairs` from `generator` to `endpoint` - Remove keypair when setting new key ### How was it tested? 1. clean ` rm -rf ~/.lisk/pos-mainchain` 2. encrypt keys `./bin/run keys:encrypt -f ./config/default/dev-validators.json` 3. import new keys `./bin/run keys:import -f config/default/dev-validators.json` 4. enable block generation `./bin/run generator:enable lsk2xxvfxaqpm42wr9reokucegh3quypqg9w9aqfo --height=0 --max-height-prevoted=0 --max-height-generated=0` 5. check block is generated (wait for 1 round) 6. check status `./bin/run generator:status --pretty`
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Expected behavior
generator:enableshould enable the block generation for specified address with parametersgenerator:enableshould have flag--use-status-valuesto use the status from the nodeActual behavior
generator:enableshould enable the block generator, but it is just setting the generator parametergenerator:importfails with missing parameterSteps to reproduce
Which version(s) does this affect? (Environment, OS, etc...)
v6.0.0-alpha.5
The text was updated successfully, but these errors were encountered: