-
Notifications
You must be signed in to change notification settings - Fork 649
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
Testnet "--private-key" command-line options is duplicated #399
Comments
Dang, that should've been fixed here - 0011d5f |
yeah, it's not exactly the same thing. What you fixed in the given commit is specifying a value for the One solution would be to not instantiate both plugins at the same time, but I don't know if |
My commit fixes the same problem you ran into, but only for the private-key option in the config file, not on the command line. I don't see a similar solution for the command line. Perhaps we should introduce namespaces for the options used by plugins, so they don't overlap. |
This issue is now in production. The reason why we need to use the command line args is this issue: #149. |
PR #443 submitted, renamed the option in |
Rename option of debug witness plugin, fix #399
Thanks, this looks indeed like the least-friction solution for now. It might not be perfect but does the job for now, so closing this issue. |
and hence cannot be specified on the command-line, as it fails with the following error:
Error parsing command line: option '--private-key' is ambiguous and matches different versions of '--private-key'
this comes from the fact the both the
witness
plugin and thedebug-witness
define the--private-key
option. A simple fix would be to rename the option for the debug-witness plugin to something like--private-key-testnet
or something to that effect.I'll submit a pull request if I can get confirmation that
--private-key-testnet
is a good naming, otherwise please suggest an alternative and I'll implement that. Thanks!The text was updated successfully, but these errors were encountered: