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

Wrong error returned (gRPC: Too low energy) #158

Open
mh-concordium opened this issue Jun 9, 2022 · 3 comments
Open

Wrong error returned (gRPC: Too low energy) #158

mh-concordium opened this issue Jun 9, 2022 · 3 comments
Labels
[Prio] Low Should be fixed if time permits but can be postponed. [Type] Bug Something isn't working

Comments

@mh-concordium
Copy link
Contributor

mh-concordium commented Jun 9, 2022

Bug Description
If user tries to delegate scheduled CCDs but doesn't have CCDs to pay for the transaction, user will receive user error (gRPC error Too low energy)

Steps to Reproduce
Try to delegate scheduled CCDs while not having any CCDs at disposal.

Expected Result
Warning before transaction is submitted that will tell that tx will fail due to not having enough CCDs.

Actual Result
image

Versions

  • Software Version: Client 4.0.3. Node 4.1.0

┆Issue is synchronized with this Jira Bug by Unito

@mh-concordium mh-concordium added [Prio] Low Should be fixed if time permits but can be postponed. [Type] Bug Something isn't working labels Jun 9, 2022
@abizjak
Copy link
Contributor

abizjak commented Jun 9, 2022

The fact that the RPC error is wrong is caused by the node, specifically this issue Concordium/concordium-node#375

The client could also check before it submits of course, and that would be a nicer user experience. But if the node provided a correct response the error would already be much less confusing.

@abizjak
Copy link
Contributor

abizjak commented Jun 23, 2022

The node issue has been fixed in Concordium/concordium-node#401 (that will be part of the ~August release).

From then on the transaction would fail immediately with a more correct error. The remaining issue here is the "check before submission".

@abizjak
Copy link
Contributor

abizjak commented Jun 23, 2022

That last part is related/duplicate of #45

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Prio] Low Should be fixed if time permits but can be postponed. [Type] Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants