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

API error message #382

Closed
abitmore opened this issue Aug 30, 2017 · 4 comments
Closed

API error message #382

abitmore opened this issue Aug 30, 2017 · 4 comments

Comments

@abitmore
Copy link
Member

abitmore commented Aug 30, 2017

We used to be able to know the exact error message when failed to broadcast a transaction from the GUI. But now:
e9077481-2e9b-4cd0-813c-f828d2c958cf

How to reproduce: try to transfer 5,000,000,000 BTS to yourself, or try to place an order in ICOWT/BTS market pair, if you're not whitelisted.

I'm not sure if it's caused by a node API change.

@abitmore
Copy link
Member Author

Perhaps an UI issue? Will also report in bitshares-ui repository.

@abitmore
Copy link
Member Author

@xeroc
Copy link
Member

xeroc commented Sep 1, 2017

This is most certainly a UI issue.
I haven't seen anything like that ever using pybitshares.

@oxarbitrage
Copy link
Member

definitely an UI issue that was changed to use the first part of the message on bitshares/bitshares-ui@762874a

if raw msg is going to be displayed i suppose it will be good to show first and second part of it.
ideal to never show the raw messages from the node in the UI, they may be of help for the experienced but ugly for newcomers, maybe just in the developer console and document it but this is another issue.

the UI is working to validate before sending, for instance it is not possible on current versions to send more asset than what you have and i hope there is a similar approach on adding a trade for an asset you are not whitelisted.

closing this.

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