New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
merge: next-costs
into next
#2956
Conversation
… connection, adding evaluated epoch to block receipt
…et current burn height in integration test
… sane-ish block height. Explicit special case for genesis block in get_epoch_of. Use Clarity epoch for read only connections
…llback_unconfirmed
Added sortition db schema transition logic
Stacks 2.05: ExecutionCost inside of StacksEpoch
2.05: use serialized_size() aggregation for cost inputs of linear methods
…s an epoch boundary, it must not have a microblock parent. It will be invalid if it does.
… microblock stream if the block it produces has a parent anchored block in a different epoch. Also, add unit tests to both the miner and consensus rules to make sure that the miner behaves this way, and a block that violates this new rule will be rejected
…t is allowed to fail
…ntegration_test to match new expected behavior
2.05 integration testing: exact costs matching in miner and follower: #2913
…coverage in vm::tests::costs
Retracting approval until all consensus bugs are fixed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a couple issues that need to be addressed before being merged, but otherwise looks great. Thanks for taking this on, @gregorycoppola!
I pushed changes to most but not all comments in case anyone wants to review. I kept the replies to one commit per comment addressed. cc @jcnelson The extra merges of "merge/nc2" into itself are because I was working in parallel from three different directories. There will be failures due to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks for bearing with us on all the PR updates.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks @gregorycoppola
Thanks for the reviews everyone! Probably harder to review than write. |
This PR merges the
next-costs
branch (Stacks 2.05) into thenext
branch (Stacks 2.1).Some code re-writes required for reasons, e.g.:
next-costs
transitions 2->2.05 andnext
transitions 2->2.1, so we need to make sure we make both transitionsnext-costs
code/tests aren't aware of ClarityVersion'sStacksEpoch
next