You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, if the operation is a proposal, the idea is that we go through each proposed operation to make sure we're accounting for the use of different fee assets.
Only the line proposalFeeAssets.push("1.3." + proposal.op[1].fee.asset_id); shouldn't have the preceeding "1.3." + because the proposal op fee asset_id is already using the "1.3.x" asset id format. As this is the case, it tries to look up the fees for "1.3.1.3.0" which is an invalid asset id.
I removed this line and the uncaught error was bypassed, so we should probably change the code to something like the following:
if (isProposal(op)) {
op[1].proposed_ops.forEach(proposal => {
proposed_ops.push(proposal);
if (
proposalFeeAssets.indexOf(
proposal.op[1].fee.asset_id
) === -1
)
proposalFeeAssets.push(proposal.op[1].fee.asset_id);
});
}
The text was updated successfully, but these errors were encountered:
When I try to create a proposal, an invalid fee asset id is created which causes an error:
get_required_fees api error: execution error: parse error: couldn't parse uint64_t
I believe this line is the source of the issue: https://github.com/bitshares/bitsharesjs/blob/develop/lib/chain/src/TransactionBuilder.js#L431
So, if the operation is a proposal, the idea is that we go through each proposed operation to make sure we're accounting for the use of different fee assets.
Only the line
proposalFeeAssets.push("1.3." + proposal.op[1].fee.asset_id);
shouldn't have the preceeding"1.3." +
because the proposal op fee asset_id is already using the "1.3.x" asset id format. As this is the case, it tries to look up the fees for "1.3.1.3.0" which is an invalid asset id.I removed this line and the uncaught error was bypassed, so we should probably change the code to something like the following:
The text was updated successfully, but these errors were encountered: