Skip to content
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

Merged
merged 560 commits into from Dec 15, 2021
Merged

merge: next-costs into next #2956

merged 560 commits into from Dec 15, 2021

Conversation

gregorycoppola
Copy link
Contributor

@gregorycoppola gregorycoppola commented Nov 30, 2021

This PR merges the next-costs branch (Stacks 2.05) into the next branch (Stacks 2.1).

Some code re-writes required for reasons, e.g.:

  • next-costs transitions 2->2.05 and next transitions 2->2.1, so we need to make sure we make both transitions
  • next-costs code/tests aren't aware of ClarityVersion's
  • new values that need to be added to structs like StacksEpoch
  • integrating support for peer versioning into next

kantai and others added 30 commits November 3, 2021 11:11
… connection, adding evaluated epoch to block receipt
… sane-ish block height. Explicit special case for genesis block in get_epoch_of. Use Clarity epoch for read only connections
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
…ntegration_test to match new expected behavior
2.05 integration testing: exact costs matching in miner and follower: #2913
@jcnelson jcnelson self-requested a review December 8, 2021 16:29
@jcnelson
Copy link
Member

jcnelson commented Dec 8, 2021

Retracting approval until all consensus bugs are fixed

Copy link
Member

@kantai kantai left a 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!

@gregorycoppola
Copy link
Contributor Author

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 reinstate panics in pox methods for NullBurnStateDB.

Copy link
Member

@kantai kantai left a 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.

Copy link
Member

@jcnelson jcnelson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks @gregorycoppola

@gregorycoppola
Copy link
Contributor Author

Thanks for the reviews everyone! Probably harder to review than write.

@gregorycoppola gregorycoppola merged commit c250655 into next Dec 15, 2021
kantai added a commit that referenced this pull request Dec 17, 2021
@kantai kantai mentioned this pull request Dec 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants