Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(blockifier): add log for cairo native execution #2868

Merged
merged 1 commit into from
Dec 23, 2024

Conversation

avivg-starkware
Copy link
Contributor

No description provided.

@reviewable-StarkWare
Copy link

This change is Reviewable

Copy link
Contributor Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@avivg-starkware avivg-starkware marked this pull request as ready for review December 22, 2024 13:36
Copy link
Contributor

@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.

Reviewable status: 0 of 1 files reviewed, 1 unresolved discussion (waiting on @avivg-starkware and @noaov1)


crates/blockifier/src/execution/execution_utils.rs line 139 at r1 (raw file):

                )
            } else {
                log::info!("Using Cairo Native execution.");

Let's log this at DEBUG level because there will be a lot of these messages and we want to be able to not see them.
+
Let add the block id and transaction hash to the message, so that we know what the message is referring to.

Suggestion:

               log::debug!("Using Cairo Native execution.");

@avivg-starkware avivg-starkware force-pushed the avivg/blockifier/add_log_native_execution branch from 4c4c2e9 to 2355384 Compare December 22, 2024 14:35
Copy link
Contributor Author

@avivg-starkware avivg-starkware left a comment

Choose a reason for hiding this comment

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

Reviewable status: 0 of 1 files reviewed, 1 unresolved discussion (waiting on @avi-starkware and @noaov1)


crates/blockifier/src/execution/execution_utils.rs line 139 at r1 (raw file):

Previously, avi-starkware wrote…

Let's log this at DEBUG level because there will be a lot of these messages and we want to be able to not see them.
+
Let add the block id and transaction hash to the message, so that we know what the message is referring to.

Done.
Making sure I'm not mistaken- by Block ID, you mean "block_number" ?

Code snippet:

context.tx_context.block_context.block_info.block_number

Copy link
Contributor

@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.

Reviewable status: 0 of 1 files reviewed, 1 unresolved discussion (waiting on @avivg-starkware and @noaov1)


crates/blockifier/src/execution/execution_utils.rs line 139 at r1 (raw file):

Previously, avivg-starkware wrote…

Done.
Making sure I'm not mistaken- by Block ID, you mean "block_number" ?

Yes. Call it block number in the message instead of block ID to avoid confusion.

@avivg-starkware avivg-starkware force-pushed the avivg/blockifier/add_log_native_execution branch from 2355384 to 4a4ac1c Compare December 22, 2024 15:15
@avivg-starkware
Copy link
Contributor Author

crates/blockifier/src/execution/execution_utils.rs line 139 at r1 (raw file):

Previously, avi-starkware wrote…

Yes. Call it block number in the message instead of block ID to avoid confusion.

Done. thanks!

Copy link
Collaborator

@noaov1 noaov1 left a comment

Choose a reason for hiding this comment

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

Reviewed 1 of 1 files at r3, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @avi-starkware)


crates/blockifier/src/execution/execution_utils.rs line 139 at r1 (raw file):

Previously, avivg-starkware wrote…

Done. thanks!

Nice. Could you please add the class hash as well? (A transaction can run multiple classes.)

@avivg-starkware avivg-starkware force-pushed the avivg/blockifier/add_log_native_execution branch from 4a4ac1c to 5bbb9f5 Compare December 23, 2024 11:28
Copy link
Contributor Author

@avivg-starkware avivg-starkware left a comment

Choose a reason for hiding this comment

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

Reviewable status: 0 of 1 files reviewed, 1 unresolved discussion (waiting on @avi-starkware and @noaov1)


crates/blockifier/src/execution/execution_utils.rs line 139 at r1 (raw file):

Previously, noaov1 (Noa Oved) wrote…

Nice. Could you please add the class hash as well? (A transaction can run multiple classes.)

Done.

Copy link
Contributor

@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.

Reviewed 1 of 1 files at r4, all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @avivg-starkware)

Copy link
Contributor

@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.

Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @avivg-starkware)

@avivg-starkware avivg-starkware force-pushed the avivg/blockifier/add_log_native_execution branch from 5bbb9f5 to 12585c8 Compare December 23, 2024 11:59
Copy link
Contributor

@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:

Reviewed 1 of 1 files at r5, all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @avivg-starkware)

@avivg-starkware avivg-starkware merged commit 855d985 into main Dec 23, 2024
11 checks passed
@avivg-starkware avivg-starkware deleted the avivg/blockifier/add_log_native_execution branch December 23, 2024 17:20
@github-actions github-actions bot locked and limited conversation to collaborators Dec 25, 2024
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