Add min balance violation to statuses in Transaction_snark.Base.User_command_failure #6448
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Recently, a constructor representing a minimum balance violation was added to
User_command_status.Failure.t
.The type
Transaction_snark.Base.User_command_failure.t
is meant to capture the ways a user command can fail, and so should mirror the type above. There was no corresponding item for a minimum balance violation.This PR adds the missing item, and uses it in
Transaction_snark.compute_unchecked
. For most transactions, it'sfalse
. For payments, theTransaction_logic
timing validator is called, and sets the value totrue
iff the there's a min balance violation.Added a comment to
User_command_status.Failure.t
to changeUser_command_failure.t
if the fields change.Note: there are other missing failure statuses in
User_command_failure.t
. I suspect that's unintentional.