Skip to content

Conversation

@AvivYossef-starkware
Copy link
Contributor

No description provided.

@reviewable-StarkWare
Copy link

This change is Reviewable

@avi-starkware
Copy link
Collaborator

crates/starknet_os_runner/src/virtual_block_executor.rs line 259 at r1 (raw file):

    /// Whether transaction validation is enabled during execution.
    pub validate_txs: bool,
}
  1. Why isn't pub(crate) sufficient here?
  2. Consider making the fields rpc_state_reader and validate_txs private if possible

Code quote:

pub struct RpcVirtualBlockExecutor {
    /// The state reader for the virtual block executor.
    pub rpc_state_reader: RpcStateReader,
    /// Whether transaction validation is enabled during execution.
    pub validate_txs: bool,
}

Copy link
Collaborator

@avi-starkware avi-starkware left a comment

Choose a reason for hiding this comment

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

@avi-starkware reviewed 1 file and all commit messages, and made 2 comments.
Reviewable status: 1 of 2 files reviewed, 3 unresolved discussions (waiting on @AvivYossef-starkware and @noaov1).


crates/starknet_os_runner/src/runner.rs line 267 at r1 (raw file):

///
/// let runner = factory.create_runner(BlockNumber(800000));
/// let output = runner.run_os(txs).await?;

run_os requires the block_number as input

Code quote:

/// let output = runner.run_os(txs).await?;

crates/starknet_os_runner/src/runner.rs line 292 at r1 (raw file):

    /// The runner is ready to execute transactions on top of the specified block.
    /// Each runner is single-use (consumed when `run_os` is called).
    pub fn create_runner(&self, block_number: BlockNumber) -> RpcRunner {

This could potentially create a mismatch with run_os if a different block_number is provided there than the number provided when creating the runner.

Code quote:

    pub fn create_runner(&self, block_number: BlockNumber) -> RpcRunner {

Copy link
Collaborator

@avi-starkware avi-starkware left a comment

Choose a reason for hiding this comment

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

@avi-starkware reviewed 1 file.
Reviewable status: all files reviewed, 3 unresolved discussions (waiting on @AvivYossef-starkware and @noaov1).

@AvivYossef-starkware AvivYossef-starkware changed the base branch from aviv/fix-async-sync-boundary to graphite-base/11581 January 13, 2026 07:50
Copy link
Contributor Author

@AvivYossef-starkware AvivYossef-starkware left a comment

Choose a reason for hiding this comment

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

@AvivYossef-starkware made 3 comments.
Reviewable status: 1 of 2 files reviewed, 3 unresolved discussions (waiting on @avi-starkware and @noaov1).


crates/starknet_os_runner/src/runner.rs line 267 at r1 (raw file):

Previously, avi-starkware (Avi Cohen) wrote…

run_os requires the block_number as input

Thanks


crates/starknet_os_runner/src/runner.rs line 292 at r1 (raw file):

Previously, avi-starkware (Avi Cohen) wrote…

This could potentially create a mismatch with run_os if a different block_number is provided there than the number provided when creating the runner.

see #11651 I think that its a better solution


crates/starknet_os_runner/src/virtual_block_executor.rs line 259 at r1 (raw file):

Previously, avi-starkware (Avi Cohen) wrote…
  1. Why isn't pub(crate) sufficient here?
  2. Consider making the fields rpc_state_reader and validate_txs private if possible

see #11652

Copy link
Collaborator

@avi-starkware avi-starkware left a comment

Choose a reason for hiding this comment

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

:lgtm:

@avi-starkware reviewed 1 file and all commit messages, made 1 comment, and resolved 3 discussions.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @noaov1).

@AvivYossef-starkware AvivYossef-starkware added this pull request to the merge queue Jan 13, 2026
Merged via the queue into main with commit 2391bf5 Jan 13, 2026
22 of 27 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Jan 15, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants