Changes for version 2.05.0.1.0 #2996

…f them

Co-authored-by: Aaron Blankstein <[email protected]>

…-blockchain into feat/hook-up-estimator

…ants, so we don't have to keep track of it in the PeerNetwork

…sting mempool queries

…sender

Feat/mempool sync

…cessed

Feat: update pessimistic cost estimator to differentiate by contract sender

…ecking to see if we're sync'ed up

…oblock push

…the next reward cycle to sync block data from by looking at the number of sortitions in the remote peer's block inventory, instead of the number of reward cycles in its PoX bit vector

…nce we bind to 0.0.0.0 but sometimes localhost resolves to ::1, leading to HTTP connection failures

…and to advertize block/microblock data

…tbound peer does not know about, push it directly to them (don't advertize it via an *Available message). Add tests to verify that push-exclusive behavior works.

… it around across burnchain syncs

…t expensive and would save us a lot of pain

…ol starts from the latest reward cycle and runs backwards; make it so that antientropy protocol restarts whenever the burnchain view changes (to force it to reconsider the latest blocks)

…on't get stuck forever

…the burnchain (even if we haven't downloaded everything yet)

…correctly infer ibd status

Feat/miner structured logging

feat: Improved Fee Rate Computation

fix: Create a separate directory for `estimates` tables

…acks-blockchain into change-log-release

docs: updated changelog with features in 2.05.0.1.0

CI: add cancel in progress behavior to PR actions

…roblock tenures

… is different than the one used to queue the original tenure. Possibly fixes #2969 as well.

…ffers from the RunTenure directive.

…the burnchain tip per the headers DB in the indexer

…ner deadlines

…r burnchain tip -- whichever is earlier -- so we don't constantly invoke the pox sync watchdog (which should only be invoked on reward cycle boundaries)

…s and chainstate databases

fix: significantly increase the speed of most RPC endpoints

… all remaining offending headers that are part of the old fork.

…ing sortition processing. Effectively 2x's the speed of a sortition.

…int out an "EXPLAIN QUERY PLAN" query for each query they execute

…StacksNode; move counters into the RunLoop; clean up arguments to both StacksNode::spawn() and spawn_*() methods. ALSO: cancel RunTenures if they finish producing a block after their targeted tip is no longer the canonical tip.

… refactor .start() into a set of different methods that carry out a specific task. Also, document them.

…thread)

…cal path

… but wants to stop sending before the socket buffer is full. Good for low-priority but expensive operations, like mempool queries

…so we don't try to send again until the next poll

…e .send() method so it stops trying to fill the socket buffer.

…t-page-id

…ocket or close it since our event loop is edge-triggered

…where we can't pull out any transactions in the alloted number of rows, or if we fill up our row allotment, we cork the stream with the last page ID so that the node can subsequently resume the query from there.

…terface

…ot 8192

…ge_id=XXX` argument, which is passed into the stream. Also, when processing a stream, expect an optional 32-byte trailer for the next page ID.

…turned next-page from mempool queries. This should alleviate node stalls on the remote peer from requesting too many transactions.

…e tests to cover new pagination

…am position

…ream stalls

… uses pagination

…etting

…tter only), and use k/v logging

… as number[]

Fix: MinedBlock event txid

…rious ways that transaction streaming can fail

…k/stacks-blockchain into feat/faster-bootup

…before advancing to the next tenure

Co-authored-by: Aaron Blankstein <[email protected]>

…unconfirmed state, and in so doing, *never* leave the MARF trie open (#2970). Confirm this with a unit test.

…we can create invalid ones for testing)

Minimize time between sortitions and block-acceptance

Chore: Update async-h1 and related dependencies

fix: download headers before instantiating burnchain

Co-authored-by: Aaron Blankstein <[email protected]>

Blockstack/pr template

Track tx_index for blocks and microblocks transactions

Fix/2970

…at the highest burnchain block header is, or return None if the DB doesn't exist yet.

…nally

…ally

…e db

…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

… it immediately begins to resume downloading stacks blocks (the current, erroneous behavior is for it to download 2100 bitcoin blocks unconditionally)

…e, in addition to doing so on instantiation

…ork/stacks-blockchain into feat/add-all-indexes

Co-authored-by: pavitthrap <[email protected]>

…on boot-up (this was only meant to forget about bans)

feat: Prometheus Block Fullness Metrics

Feat/add all indexes

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

Update changelog

#2987 to be added next release

updating metrics for issue 2987

Release 2.05.0.1.0 merge

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Changes for version 2.05.0.1.0 #2996

Changes for version 2.05.0.1.0 #2996

Commits on Jan 3, 2022

Commits on Jan 4, 2022

Commits on Jan 5, 2022

Commits on Jan 6, 2022

Commits on Jan 7, 2022

Commits on Jan 9, 2022

Commits on Jan 10, 2022

Commits on Jan 11, 2022

Commits on Jan 12, 2022

Commits on Jan 13, 2022

Commits on Jan 14, 2022

Commits on Jan 15, 2022

Commits on Jan 16, 2022

Commits on Jan 17, 2022

Commits on Jan 18, 2022

Commits on Jan 19, 2022

Commits on Jan 20, 2022

Commits on Jan 21, 2022

Commits on Jan 22, 2022

Commits on Jan 24, 2022

Commits on Jan 25, 2022

Commits on Jan 26, 2022

Commits on Jan 27, 2022

Commits on Jan 28, 2022

Commits on Jan 31, 2022

Commits on Feb 1, 2022

Commits on Feb 3, 2022

Commits on Feb 4, 2022

Commits on Feb 7, 2022