bitshares-ui: [2] Show reason why a proposal has failed to execute

Is your feature request related to a problem? Please describe. Now a failed proposal only shows a “failed” status but does not show the reason. With the latest core release, it’s possible to get the reason: proposal_object now have a fail_reason field.

Describe the solution you’d like A clear and concise description of what you want to happen.

Describe alternatives you’ve considered A clear and concise description of any alternative solutions or features you’ve considered.

Additional context Add any other context or screenshots about the feature request here.

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 1
Comments: 15 (15 by maintainers)

Most upvoted comments

@startailcoon i’ve put it into tooltip. Havent tested it on mainnet, but in case node version is not >= 3.1.0 there would be empty message. Can we increase the bounty to 2 hours? it took a little bit more time to detect the problem first

Increased

startailcoon on May 28, 2019

This was blocked by a core issue that was fixed in 3.1.0. Do we have any results on this so we can merge it to main network yet?

startailcoon on May 22, 2019

The feature release is currently being deployed on testnet, once that is done you can start on this again.

sschiessl-bcp on May 3, 2019

@sschiessl-bcp to my great regret last commiter forget to add fail_reason field into reflection meta of proposal_object.hpp, so proposals get serialized without that field, and this field is not accessible over rpc api. It took ~2 hours for me to find the problem 😃

Created an issue https://github.com/bitshares/bitshares-core/issues/1730

dot5enko on Apr 22, 2019

Set one up with review period, and approve it. Set one up that transfers more than you have, and approve.

sschiessl-bcp on Apr 18, 2019