Skip to content

Conversation

@akundaz
Copy link
Contributor

@akundaz akundaz commented Aug 4, 2025

πŸ“ Summary

Record how many flashblocks we missed

πŸ’‘ Motivation and Context

We're not recording this metric properly at the moment


βœ… I have completed the following steps:

  • Run make lint
  • Run make test
  • Added tests (if applicable)

@akundaz akundaz self-assigned this Aug 4, 2025
@akundaz akundaz force-pushed the ak-record-missing-flashblocks branch from 5ab320e to a36aa21 Compare August 6, 2025 14:05
target: "payload_builder",
message = message,
missing_flashblocks = flashblocks_per_block.saturating_sub(ctx.flashblock_index()),
reduced_flashblocks = self.config.flashblocks_per_block().saturating_sub(flashblocks_per_block),
Copy link
Collaborator

Choose a reason for hiding this comment

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

instead of the number of missing flashblocks I would have the raw values e.g. flashblocks_per_block, flashblock_index and flashblocks per block as the flashblocks_per_block and ctx.flashblock_index() values can potentially change for every block

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure, there are two flashblocks_per_block values though so I named one of them config_flashblocks_per_block. Is there a better name for that?

@akundaz akundaz requested a review from avalonche August 6, 2025 15:48
@SozinM SozinM merged commit bb31c69 into main Aug 7, 2025
4 checks passed
@SozinM SozinM deleted the ak-record-missing-flashblocks branch August 7, 2025 06:34
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.

3 participants