Skip to content
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

[cli_wallet] exception: bad_function_call (no default websocket endpoint) #3597

Open
Gandalf-the-Grey opened this issue Feb 7, 2020 · 5 comments
Assignees

Comments

@Gandalf-the-Grey
Copy link
Contributor

When you start cli_wallet without explicitly stating -s a.k.a. --server-rpc-endpoint which supposed to have default value ( [=arg(=ws://127.0.0.1:8090)] ) you get a confusing error while trying to use any remote command such as info.

Starting cli_wallet with explicitly stating -sws://127.0.0.1:8090 works fine.

@mvandeberg
Copy link
Contributor

Is this on master?

@Gandalf-the-Grey
Copy link
Contributor Author

Yes, current master (6412e735)

@mvandeberg
Copy link
Contributor

The behavior is intentional. We added the ability for the wallet to do offline signing. We could change how offline signing is enabled, perhaps with an --offline option that ignores the previous default argument. In your opinion, would that be better UX?

@Gandalf-the-Grey
Copy link
Contributor Author

I saw that, offline signing is cool. 👍
Yes, keeping default behavior the same + --offline seems more intuitive

@mvandeberg
Copy link
Contributor

Will address this before the SMT release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants