Skip to content

refactor: start cleaning up execution info#526

Open
akundaz wants to merge 4 commits into
mainfrom
ash-mvwvwnxqsttt
Open

refactor: start cleaning up execution info#526
akundaz wants to merge 4 commits into
mainfrom
ash-mvwvwnxqsttt

Conversation

@akundaz
Copy link
Copy Markdown
Contributor

@akundaz akundaz commented May 21, 2026

Just a few small refactors in this PR:

  • cleaning up limit checking
  • moving last fb index from fb state type into execution info

Budgeting refactor still in progress

@akundaz akundaz self-assigned this May 21, 2026
@akundaz akundaz requested a review from julio4 May 21, 2026 23:58
Copy link
Copy Markdown
Member

@julio4 julio4 left a comment

Choose a reason for hiding this comment

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

I don't think ExecutionInfo is the right place to keep track of flashblocks index. I would prefer if possible splitting in object of same lifecycle: one for the slot/payload, one per flashblock.

budget check functions are nice but we could do even more, what do you have in mind for "Budgeting refactor still in progress"?

Rest looks good!


use super::{ExecutionInfo, TxnExecutionResult};

fn execution_info_with_uncompressed_bytes(cumulative_uncompressed_bytes: u64) -> ExecutionInfo {
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

nit: you can also add a implementation on ExecutionInfo under test cfg to do ExecutionInfo::with_uncompressed_bytes

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.

2 participants