-
Notifications
You must be signed in to change notification settings - Fork 33
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(l2): forbid expects #1289
Conversation
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.
If we run the stack with the following steps:
cd crates/l2
cp .env.example .env
make init
- do
ctrl-c
to stop the server, in order to restart it without some env variables. - Comment some env variables starting with
COMMITTER
,L1_WATCHER
,PROPOSER
... etc make init-l2
It will not throw an error nor a message saying that there are missing variables. We should throw an error message and even stop the execution saying that some config variables are missing.
750c5d6
to
eba775d
Compare
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.
Inside the zkvm
dir we can use expect
to avoid the compilation error
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.
LGTM, ready to merge if the CI passes. Just make sure that type SetupResult
is a struct
. in PR #1290 or in this one.
ef9a27f
to
f318cde
Compare
…ge in all submodules.
…e was too complex.
f318cde
to
bfa18a7
Compare
Motivation
We should not be using
.expect()
and use Errors instead.Description
expect_used = "deny"
was added toCargo.toml
to throw clippy errors on expects..expect()
usage was replaced with errorsCloses #1267