fix: fix mismatch between validator_count & metrics gazer #223
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
leoporoli
approved these changes
Sep 22, 2023
h4ck3rk3y
pushed a commit
that referenced
this pull request
Sep 26, 2023
🤖 I have created a release *beep* *boop* --- ## [0.3.1](0.3.0...0.3.1) (2023-09-26) ### Features * add blobspammer ([f166d71](f166d71)) * add blobspammer ([#165](#165)) ([f166d71](f166d71)) * add support for electra ([#176](#176)) ([fbe6c00](fbe6c00)) * Add Tx_spamer_params and move MEV to the bottom of main.star ([#208](#208)) ([23628b2](23628b2)) * added a reliable flooder ([#186](#186)) ([8146ab7](8146ab7)) * all_el_metrics ([#195](#195)) ([3bbcca7](3bbcca7)) * Allow selection of additional services ([#220](#220)) ([57b15fe](57b15fe)) * Make args optional ([#190](#190)) ([a3ad030](a3ad030)) * pass slots per epoch to mev-boost-relay ([#188](#188)) ([14acb6f](14acb6f)) ### Bug Fixes * bring back wait for capella fork epoch ([#212](#212)) ([c7cce7e](c7cce7e)) * bug with participant counts that lead to more than needed participants ([#221](#221)) ([7b93f1c](7b93f1c)) * dont wait for epoch 1 and launch MEV before tx-fuzz ([#210](#210)) ([8b883af](8b883af)) * fail capella fork epoch ([#196](#196)) ([ebff2d0](ebff2d0)) * fix mismatch between validator_count & metrics gazer ([#223](#223)) ([5dd4f9b](5dd4f9b)) * Improve MEV setup to use less containers for non_validator nodes ([#224](#224)) ([bd176f0](bd176f0)) * Kevin/postgres package upgrade ([#179](#179)) ([1bcc623](1bcc623)) * Kevin/unpin redis version ([#182](#182)) ([4eb7127](4eb7127)) * lodestar flag ([#217](#217)) ([5f1e0f2](5f1e0f2)) * mev should work with the validator count change ([#225](#225)) ([37dccce](37dccce)) * mev-boost creation by making it depend on actual participant count ([#191](#191)) ([7606cff](7606cff)) * Mock builder updates ([#193](#193)) ([6cc3697](6cc3697)) * parse input ([#205](#205)) ([a787b38](a787b38)) * pass through env var now for builder_signing_tx_key ([#207](#207)) ([a63f2fd](a63f2fd)) * Pin Redis version in prep for package catalog version upgrade ([#180](#180)) ([09b235a](09b235a)) * remove hardcoding of addresses in MEV flood ([#184](#184)) ([21b0975](21b0975)) * replace plan.assert with plan.verify ([#202](#202)) ([073135d](073135d)) * start boost immediately after relay starts running ([#213](#213)) ([b6ce1e9](b6ce1e9)) * update readme for MEV params ([#189](#189)) ([c1bf13e](c1bf13e)) * use 4th private key (index 3) for tx fuzz like before ([#215](#215)) ([1752ed0](1752ed0)) * use the third address instead of coinbase for tx-fuzz ([#185](#185)) ([3b2993c](3b2993c)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.