operation_history_object::virtual_op
numbering may be discontinuous (possibly with holes)
#2692
Open
2 of 17 tasks
Labels
Milestone
Bug Description
In
database::push_applied_operation()
, after_current_virtual_op
is assigned tovirtual_op
of the newly createdoperation_history_object
,_current_virtual_op++
is called:bitshares-core/libraries/chain/db_block.cpp
Lines 535 to 544 in f812666
If the operation being pushed is in a proposal, after it is added to
_applied_ops
, it may be removed later if the proposal fails, but_current_virtual_op
is not updated back:bitshares-core/libraries/chain/db_block.cpp
Lines 361 to 364 in f812666
I'm not sure if it is worth fixing.
#1675 is related.
Impacts
Describe which portion(s) of BitShares Core may be impacted by this bug. Please tick at least one box.
Host Environment
Please provide details about the host environment. Much of this information can be found running:
witness_node --version
.6.0.2
CORE TEAM TASK LIST
The text was updated successfully, but these errors were encountered: