-
Notifications
You must be signed in to change notification settings - Fork 206
Enforce_disable_trace_padding_used_only_in_proof_mode #1984
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
Enforce_disable_trace_padding_used_only_in_proof_mode #1984
Conversation
b96ae47 to
b92d256
Compare
|
|
Benchmark Results for unmodified programs 🚀
|
b92d256 to
46c82e6
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1984 +/- ##
==========================================
- Coverage 96.53% 96.53% -0.01%
==========================================
Files 103 103
Lines 42599 42612 +13
==========================================
+ Hits 41123 41135 +12
- Misses 1476 1477 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
yuvalsw
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 4 of 4 files at r1, all commit messages.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @fmoletta, @gabrielbosio, @igaray, @juanbono, @OmriEshhar1, @Oppen, and @pefontana)
vm/src/tests/cairo_run_test.rs line 1038 at r1 (raw file):
let mut hint_processor = BuiltinHintProcessor::new_empty(); let runner = cairo_run(program_data, &config, &mut hint_processor).unwrap(); assert!(!runner.vm.current_step.is_power_of_two());
- I don't understand how this is equivalent to the previous check you deleted.
- it is not guaranteed to not be a power of 2. Add a comment saying this is true for this proof specifically (assuming I am right about it).
vm/src/vm/runners/cairo_runner.rs line 5416 at r1 (raw file):
Err(RunnerError::DisableTracePaddingWithoutProofMode) => { /* test passed */ } _ => panic!("Expected DisableTracePaddingWithoutProofMode error"), }
consider (will also probably dismiss the codecov failure)
Suggestion:
assert_eq!(result, Err(RunnerError::DisableTracePaddingWithoutProofMode), "Expected DisableTracePaddingWithoutProofMode error");46c82e6 to
6b89371
Compare
YairVaknin-starkware
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @fmoletta, @gabrielbosio, @igaray, @juanbono, @OmriEshhar1, @Oppen, @pefontana, and @yuvalsw)
vm/src/tests/cairo_run_test.rs line 1038 at r1 (raw file):
Previously, yuvalsw wrote…
- I don't understand how this is equivalent to the previous check you deleted.
- it is not guaranteed to not be a power of 2. Add a comment saying this is true for this proof specifically (assuming I am right about it).
- it's not. the prev test didn't really test anything and especially not what its name implies. It didn't even run in proof mode (which with the change introduced in this PR will fail).
- Correct. Done.
vm/src/vm/runners/cairo_runner.rs line 5416 at r1 (raw file):
Previously, yuvalsw wrote…
consider (will also probably dismiss the codecov failure)
Was my first approach, too, but the CairoRunner struct doesn't impl Debug, and it would require deriving it for many structs that are internally used by the Runner struct just for that for this approach to work.
3605efc to
708987e
Compare
TITLE
Description
Description of the pull request changes and motivation.
Checklist
This change is