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
In our BlockMachine implementation, we already have this code which should make sure that no two blocks are added for the same input / output pair.
The problem is that it only looks into the last block. If other blocks have been added in the mean time, a new block would be created if the same connecting identity was processed again.
This currently causes the permutation_to_block_to_block test to fail.
The text was updated successfully, but these errors were encountered:
Just like the `VmProcessor`, with this PR the `BlockProcessor` never
processes an identity again that has been completed.
This should be a slight performance optimization (when the "default"
sequence iterator is used), but more importantly it:
- Fixes#1385
- Allows us to remove error-prone code (see below)
- Helps with witgen for stateful machines, like those who access memory
In our
BlockMachine
implementation, we already have this code which should make sure that no two blocks are added for the same input / output pair.The problem is that it only looks into the last block. If other blocks have been added in the mean time, a new block would be created if the same connecting identity was processed again.
This currently causes the
permutation_to_block_to_block
test to fail.The text was updated successfully, but these errors were encountered: