* fix: web3.js test typescript errors
Fixes the typescript errors throughout the
web3.js test suite
* fix: node14 test
AbortController is a default in node16 but needs
to be imported for node14
* fix: additional typescript errors
Adds the tests to the tsconfig to auto-include mocha
and fixes remaining typescript errors
* fix: graphql-tools to work with typescript
version of graphql-tools initially installed has incompatible
types preventing ./scripts/typegen.sh from passing when tests
are added to the include path of tsconfig.json
* Don't build typedefs for tests
Co-authored-by: steveluscher <me+github@steveluscher.com>
The commit allocates 2% of slots to running experiments with different
turbine fanouts based on the slot number.
The experiment is feature gated with an additional feature to disable
the experiment.
* Plumb dumps from replay_stage to repair
When dumping a slot from replay_stage as a result of duplicate or
ancestor hashes, properly update repair subtrees to keep weighting and
forks view accurate.
* add test
* pr comments
* Bump sbf-tools to v1.32
This version of sbf-tools is based on Rust 1.65.0 and LLVM 15.0.
* Temporary ignore build-sbf tests until issue with buildkite cache resolved
* feat: allow for verifying the sigs of partially signed txs
* fix: make comment ab verifying sigs more specific
Co-authored-by: Steven Luscher <steveluscher@users.noreply.github.com>
* feat: add tests for partial signed tx verification
* fix: revert lockfile changes
* fix: make tests more modular
* fix: run linter
Co-authored-by: Steven Luscher <steveluscher@users.noreply.github.com>
Currently, if starting-slot is unspecified, a value of 0 will be chosen.
In the common case where someone is operating on a much more recent
range, this would result in a ton of wasted operations & time.
Instead, choose a smarter default value for starting-slot based on what
we detect is currently in the blockstore.
* vote: Prevent commission update in the second half of epochs
* Address feedback
* Fix tests
* Make the feature enabled by single-contributor
* Use a cooler pubkey
ConnectionCache is being used for managing connections for sending messages using quic. In the current implementation the connection's endpoint is created in a lazy initialized fashion and set to one per connection pool. In repair we need all connections to use the same Endpoint so that the server can send back the response to the same Endpoint.
* Add metrics for min/max priority fee per slot, and counters for fee/non-fee txs
* get fee range of prioritized transactions only
* Update runtime/src/prioritization_fee.rs
Co-authored-by: Trent Nelson <trent.a.b.nelson@gmail.com>
* Update runtime/src/prioritization_fee.rs
Co-authored-by: Trent Nelson <trent.a.b.nelson@gmail.com>
* fix format
Co-authored-by: Trent Nelson <trent.a.b.nelson@gmail.com>
TJDawson10
gr8den
behzad nouri
Steven Luscher
kirill lykov
Ashwin Sekar
Dmitri Makarov
Yihau Chen
Nico Schapeler
steviez
Tyera
Daniel Kilimnik
Jon Cinque
dependabot[bot]
Lijun Wang
Brian Anderson
Alessandro Decina
Nick Frostbutter
Jeff Washington (jwash)
Tao Zhu
Brooks