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.

Sign up for GitHub

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

Jump to bottom

Suggest to optimize double-spending error prompt #271

Open
Dawn-githup opened this issue Feb 16, 2023 · 1 comment
Open

Suggest to optimize double-spending error prompt #271

Dawn-githup opened this issue Feb 16, 2023 · 1 comment
Assignees
@oriole-pub
Labels
P-Low

Comments

@Dawn-githup
Copy link

Steps to reproduce the behavior:

1.Initiate multiple transactions in succession
2.Error prompt:Unknown Error, Please try again later

Error: {"code":-301,"message":"TransactionFailedToResolve: Resolve failed Unknown(OutPoint(0x716d254d7cf85b26e83664a0ef89820126e344cfa8b3288855d3bcc10464928a01000000))","data":"Resolve(Unknown(OutPoint(0x716d254d7cf85b26e83664a0ef89820126e344cfa8b3288855d3bcc10464928a01000000)))"}

The current error prompt is not detailed enough, and the prompt information needs to be optimized
@ShookLyngs ShookLyngs changed the title Suggest to optimize double flower error prompt Suggest to optimize double-spending error prompt Feb 16, 2023
@oriole-pub oriole-pub self-assigned this Feb 17, 2023
@Flouse Flouse added the P-Low label Feb 17, 2023
@oriole-pub
Copy link
Collaborator

This issue will be solved on #274

@oriole-pub oriole-pub mentioned this issue Mar 1, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@oriole-pub oriole-pub

Labels
P-Low
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: Support sending multiple transactions
3 participants
@Flouse @Dawn-githup @oriole-pub