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.

Sign up for GitHub

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

Jump to bottom

Changes for version 2.05.0.1.0 #2996

Merged
merged 465 commits into from
Feb 7, 2022
Merged

Changes for version 2.05.0.1.0 #2996

merged 465 commits into from
Feb 7, 2022

Conversation

pavitthrap
Copy link
Contributor

@pavitthrap pavitthrap commented Jan 12, 2022 •
edited
Loading

This PR merges changes from develop into master for version 2.05.0.1.0 of the stacks node.

Release Checklist

  • The release must be timed so that it does not interfere with a prepare phase
  • Before creating the release, the release manager must determine the version number for this release. This is a minor release, incrementing the minor version number: 2.05.0.1.0
  • This release is blocked on these PRs:
  • The release manager must update the CHANGELOG.md file with summaries what was Added, Changed, and Fixed.
  • Release candidate tag has been built
  • Once the release candidate has been built, and docker images, etc. are available, the release manager will notify various ecosystem participants to test the release candidate on various staging infrastructure:
    • Stacks Foundation staging environments.
    • Hiro PBC testnet network.
    • Hiro PBC mainnet mock miner.
  • The release candidate should be announced in the #stacks-core-devs channel in the Stacks Discord.
  • The release manager will test that the release candidate successfully syncs with the current chain from genesis.
  • Once the final release candidate has rolled out successfully without issue on the above staging infrastructure, the release manager tags 2 additional stacks-blockchain team members to review the release PR.

Greg Coppola and others added 30 commits January 3, 2022 15:48
remove bad comment
55160da
remove extra comment
dbd1613
fuzz each eleement by the same factor
a53f48a
added tests to yml file
5826417
remove new estimator from the toml file; wait till we add it to all o…
3c93a6c 
…f them
remove make_block_receipt
e9afd2d
replaced 0.5 with 0.1 as the fraction, changed variable name
0ad5063
Merge branch 'develop' into feat/hook-up-estimator
5428f96
mark make_block_receipt as for test
94f2c90
add constant MINIMUM_TX_FEE_RATE
b77f5a8
panic if weight is 0f64
b76585d
added changelog
b045302
added fuzzer options to config structs
eca6e01
added the config options so they are used now
2ceffad
updated integration test to use parameters
9f03d8c
added to the README
913f03e
fixed the names in bitcoin-tests
3cad19e
@gregorycoppola @kantai
Update README.md
c8e9bc4 
Co-authored-by: Aaron Blankstein <[email protected]>
@gregorycoppola @kantai
Update README.md
ba534b3 
Co-authored-by: Aaron Blankstein <[email protected]>
remove "now defaulting to this" in CHANGELOG
c22ba1e
Merge branch 'feat/hook-up-estimator' of github.com:blockstack/stacks…
b26fb4c 
…-blockchain into feat/hook-up-estimator
use expect not unwrap
0332ece
changed config options to be Option's
281ed4c
fix test comments
cda4f08
update default handling
b2913de
@jcnelson
fix: update comments to reflect code behavior
ceae2f5
@jcnelson
refactor: keep mempool state-machine sync state within the state vari…
e3b9183 
…ants, so we don't have to keep track of it in the PeerNetwork
@jcnelson
chore: comment that transaction creation in the boilerplate is for te…
b7c77e9 
…sting mempool queries
@jcnelson
Merge branch 'develop' into feat/mempool-sync
dbf910c
@kantai
feat: update pessimistic cost estimator to differentiate by contract …
37fcaac 
…sender
jcnelson and others added 24 commits January 31, 2022 17:38
@jcnelson
fix: instantiate indexes separately from tables and do so uncondition…
2ec678f 
…ally
@jcnelson
fix: instantiate indexes unconditionally and do so separately from th…
d147934 
…e db
@jcnelson
fix: during IBD, try to begin neighbor walks with *bootstrap* peers, …
2f8b546 
…not just peers we've seen before and haven't banned yet. This ensures that a node quickly resumes downloading blocks if it gets stopped and restarted during ibd
@jcnelson
chore: plumb through ibd flag to neighbor state-machine
284e92e
@jcnelson
fix: make it so that when a node stops and restarts during bootstrap,…
c08a6c3 
… it immediately begins to resume downloading stacks blocks (the current, erroneous behavior is for it to download 2100 bitcoin blocks unconditionally)
@jcnelson
Merge branch 'develop' into feat/add-all-indexes
93dc371
@jcnelson
fix: create indexes when connecting to the database in read/write mod…
509f209 
…e, in addition to doing so on instantiation
@jcnelson
Merge branch 'feat/add-all-indexes' of https://github.com/stacks-netw…
41717c1 
…ork/stacks-blockchain into feat/add-all-indexes
@gregorycoppola @pavitthrap
kantai's suggestion for src/chainstate/stacks/db/blocks.rs
ba45e6f 
Co-authored-by: pavitthrap <[email protected]>
Merge branch 'develop' into feat/prometheus-fullness
4be27a3
collapse the "check mempool feature" checks
b88d8ce
@jcnelson
fix: don't set peers to always-allowed when resetting allowed status …
8e341fa 
…on boot-up (this was only meant to forget about bans)
@gregorycoppola
Merge pull request #3025 from stacks-network/feat/prometheus-fullness
ff18dfc 
feat: Prometheus Block Fullness Metrics
@pavitthrap
Merge branch 'develop' into feat/add-all-indexes
890f121
@jcnelson
Merge pull request #3029 from stacks-network/feat/add-all-indexes
8c7dc19 
Feat/add all indexes
@pavitthrap
Docs: updated changelog
ba627d5
@wileyj
updating metrics for issue 2987
2a0f1bc 
2 metrics weren't as correct as they should be.
- `stacks_node_stacks_tip_height` was moved to the relayer. in tests, this proved to be a more effective location to track the data vs what `/v2/info` was reporting
- moved `stacks_node_neighbors_*` out of the pruning loop. this resulted in the metric being set more often, but the actual count of neighbors was far more accurate when compared to `/v2/neighbors`
- no changes were made to the mempool tx metric, to get this more accurate will be a far heavier lift. leaving for future work
- script used for testing: https://gist.github.com/wileyj/881eda423366134bc25e3fb5ec39ccbb
@pavitthrap
Merge pull request #3032 from stacks-network/docs-update-changelog
6c900ce 
Update changelog
@wileyj
Adding changelog entry for unreleased changes
571a486 
#2987 to be added next release
@wileyj
Merge branch 'develop' into fix/2987
8c8b999
@kantai
move changelog entry to 2.05.0.1.0
290db1d
@kantai
Merge pull request #3033 from stacks-network/fix/2987
3f47def 
updating metrics for issue 2987
@pavitthrap
Merge branch 'master' into release-2.05.0.1.0-merge
59a4429
@pavitthrap
docs: update changelog and readme
c252794
kantai
kantai approved these changes Feb 7, 2022
View reviewed changes
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! Just needs to merge #3036

jcnelson
jcnelson approved these changes Feb 7, 2022
View reviewed changes
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!

@pavitthrap pavitthrap merged commit de541f9 into master Feb 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jcnelson jcnelson jcnelson approved these changes

@kantai kantai kantai approved these changes

@gregorycoppola gregorycoppola Awaiting requested review from gregorycoppola

Assignees
No one assigned
Labels
release 2.05.0.1.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
8 participants
@pavitthrap @kantai @jcnelson @CLAassistant @gregorycoppola @CharlieC3 @hstove @wileyj