-
Notifications
You must be signed in to change notification settings - Fork 64
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
GUI: setting a too high feerate for a Spend crashes the software #822
Comments
In relation to the |
Can we just add a max feerate value for now, something like 1000 ? |
What's wrong with @jp1ac4's suggestion? Do you think it would necessitate a lot more work? |
I do not understand how it prevent the user to put a too big feerate and stop the multiplication, it is not clear for me. |
Well i think in this case you don't have the multiplication anymore since you use the result from |
OK understood now. |
We did forget that we have our RPC interface in the way for separate GUI and daemon. |
It's already doing that for the coin selection though? |
mmmh we may have a bug then, I am afraid that CoinSelectionError is not serialized correctly from the gui when receiving a RPC error from the daemon. I am trying right now |
What do you mean? |
Error while doing a spend with a detached daemon and gui: When the daemon is embedded (not distant) the CoinSelectionError is correctly passed as DaemonError::CoinSelection When the daemon is distant and we have rpc communication, the error is received as DaemonError::RpcError |
Indeed, overlooked the detached daemon mode. We could use the JSONRPC error |
Yes, GUI would directly call the |
…oin selection a732468 spend: check max feerate (edouardparis) 4ccecd1 Use create_spend to calculate amount left to select (edouardparis) Pull request description: Fixes #822. based on #865 ACKs for top commit: jp1ac4: ACK a732468. Tree-SHA512: aa2728218d9ccf7b6511f881d88b262522705b4162b5b4235560626ee8b5b8c6d57e743ebfaf85dc633d6e3d2380badfe354a6dc4d19b89d3f380c63e123704e
1339898 commands: include missing amount in response (jp1ac4) Pull request description: This PR follows a discussion around #873 (comment). The GUI uses the `InsufficientFunds` error to get the missing amount when the user is creating a new spend, but it is not straightforward to extract this information in a general way from the RPC error (see #822 (comment)) and instead the spend module's `create_spend` is currently used (see #863). With this PR, the missing amount will be included in the `createspend` response rather than as an error. These changes are based on suggestions from @darosior and @edouardparis. In a follow-up PR, the GUI should revert to using the `createspend` command to calculate the amount left to select. ACKs for top commit: darosior: re-ACK 1339898 Tree-SHA512: bf702d6b355339e96e719c1d95824e7941ac4fbaece4ec4cccd00b56ea4683ce7fb0cefc43faa5731b57e7935ef99da3a2c73b84aaeb9fa5f67703c799be2196
We should really avoid careless conversions. Or idk sanitize inputs.
liana/gui/src/app/state/spend/step.rs
Lines 173 to 236 in 514535d
The text was updated successfully, but these errors were encountered: