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

cannon: Output information about the state in JSON format from the witness command #12137

Merged
merged 2 commits into from
Sep 26, 2024

Conversation

ajsutton
Copy link
Contributor

Description

Will provide all the information about a state that the challenger needs so it doesn't have to depend on the parsing code directly.

Also set the default target for make to cannon - previously it was just building cannon-impl so the bin/cannon command didn't get updated.

@ajsutton ajsutton requested review from a team as code owners September 25, 2024 23:06
Copy link
Contributor

semgrep-app bot commented Sep 25, 2024

Semgrep found 35 sol-style-return-arg-fmt findings:

Named return arguments to functions must be appended with an underscore (_)

Ignore this finding from sol-style-return-arg-fmt.

Semgrep found 44 sol-style-input-arg-fmt findings:

Inputs to functions must be prepended with an underscore (_)

Ignore this finding from sol-style-input-arg-fmt.

Copy link

codecov bot commented Sep 25, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.94%. Comparing base (4680790) to head (d14c9b2).
Report is 14 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop   #12137      +/-   ##
===========================================
- Coverage    75.16%   74.94%   -0.22%     
===========================================
  Files           49       49              
  Lines         3652     3652              
===========================================
- Hits          2745     2737       -8     
- Misses         734      743       +9     
+ Partials       173      172       -1     
Flag Coverage Δ
cannon-go-tests 74.94% <ø> (-0.22%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
cannon/multicannon/witness.go 0.00% <ø> (ø)

... and 1 file with indirect coverage changes

…tness command.

Will provide all the information about a state that the challenger needs so it doesn't have to depend on the parsing code directly.
@ajsutton ajsutton force-pushed the aj/cannon-make-proof branch from 3a17fb3 to b324826 Compare September 26, 2024 03:39
Copy link
Contributor

@Inphi Inphi left a comment

Choose a reason for hiding this comment

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

This is OK. Is the printed state data printed to stdout needed by the op-challenger? If so, we should write to a file instead.
It's not too late to break the cannon CLI.

@Inphi
Copy link
Contributor

Inphi commented Sep 26, 2024

This is OK. Is the printed state data printed to stdout needed by the op-challenger? If so, we should write to a file instead. It's not too late to break the cannon CLI.

Nvmind this. The witness subcommand is simple enough that I'm not too concerned with a random logger breaking stdout.

@ajsutton ajsutton added this pull request to the merge queue Sep 26, 2024
Merged via the queue into develop with commit c8afa15 Sep 26, 2024
67 checks passed
@ajsutton ajsutton deleted the aj/cannon-make-proof branch September 26, 2024 20:39
samlaf pushed a commit to samlaf/optimism that referenced this pull request Nov 10, 2024
…tness command (ethereum-optimism#12137)

* cannon: Output information about the state in JSON format from the witness command.

Will provide all the information about a state that the challenger needs so it doesn't have to depend on the parsing code directly.

* cannon: Update multicannon witness description.
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