Add fail reason to proposal object

[abitmore]

For better UX, we can add a new field in proposal_object to indicate why a proposal had failed to execute.

• this feature
• after done, submit an issue to bitshares-ui repository to use this feature

[abitmore]

Just a note: @xeroc is working on this.

[xeroc]

The problem with this ticket is that proposals are only in the database as long as they are not expired or executed. That lead us to implement a plugin for persistent proposals (for PeerPlays specifically). This plugin is currently extended to also handle exceptions.
However, as I discussed with @pmconrad yesterday, the plugin can not nicely deal with roll-backs or nested proposals.

[abitmore]

@xeroc persistent proposal is another topic which is out of scope of this issue. In this issue we'll focus on active proposals but not expired ones.

OP is clear: add a new field in proposal_object to indicate why a proposal had failed to execute. If you're going this way, please proceed; otherwise please unassign yourself or leave a message so others will know to work on it.

[xeroc]

I have unassigned myself.

[ryanRfox]

@jmjatlanta I believe that because this is merged it should be marked Closed as well. I'll allow you to do that when appropriate. Thank you for moving to Done. In the future, you may automate this: https://blog.github.com/2013-05-14-closing-issues-via-pull-requests/

[jmjatlanta]

Learn something new every day. Thanks!