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
Here are some data we follow throughout a conflation that we currently don't pop with popped transactions, but which we should just so as to be clean.
DeploymentInfo
To some extent this doesn't matter now since blocks are first sequenced (and for sequencing this popping doesn't matter) and there may always be a first round before trace production. But logically this is an oversight. And would come across as such to anyone reviewing the code. Plus this would be a place where we could add unit tests for the deployment numbers and statuses: pop a transaction that performs some deployment, redeploy in the next transaction.
The text was updated successfully, but these errors were encountered:
Here are some data we follow throughout a conflation that we currently don't pop with popped transactions, but which we should just so as to be clean.
DeploymentInfo
To some extent this doesn't matter now since blocks are first sequenced (and for sequencing this popping doesn't matter) and there may always be a first round before trace production. But logically this is an oversight. And would come across as such to anyone reviewing the code. Plus this would be a place where we could add unit tests for the deployment numbers and statuses: pop a transaction that performs some deployment, redeploy in the next transaction.
The text was updated successfully, but these errors were encountered: