-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix:cli:Continue instead of return error if no valid value is filled #8131
Conversation
Bug fixed : if hitting return instead of filling with a valid value, the CLI crashed (line 796) Change return err by continue to ask a valid value again
Bug fixed : if hitting return instead of filling with a valid value, the CLI crashed (line 796) Change return err by continue to ask a valid value again
Commit to fix lint reported errors during tests on CircleCI (remove blank lines x2)
Commit to fix lint reported errors during tests on CircleCI (remove trailling whitespace)
Codecov Report
@@ Coverage Diff @@
## master #8131 +/- ##
==========================================
- Coverage 39.39% 39.33% -0.06%
==========================================
Files 666 666
Lines 72466 72469 +3
==========================================
- Hits 28546 28505 -41
- Misses 38995 39027 +32
- Partials 4925 4937 +12
Continue to review full report at Codecov.
|
Clear the list of miner addresses and successfull get-asked before asking for new ones Previous behavior : if get-ask failed for miner(s), the faulty miner will be retried each time, so you have to stop the command and start again to change this faulty miner (instead of removing from the list on the new attempt)
For deal count, yeah, that makes sense, though I'd make that 3, at least, so that there is at least some default redundancy. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Related Issues
Fixes #8100
Proposed Changes
If no valid value are filled in "Deals to make (1)", display an error message and continue to ask
(instead of return error to make the CLI crash)
Additional Info
Maybe we can force a default value to 1, instead of asking in loop for a valid value ?