10000 fix: exit with nonzero code on init cmd error by marcelo-gonzalez · Pull Request #8334 · near/nearcore · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

fix: exit with nonzero code on init cmd error #8334

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

Merged
merged 2 commits into from
Jan 11, 2023

Conversation

marcelo-gonzalez
Copy link
Contributor

#5967 refactored things so that the init command wouldn't panic on normal/expected errors, but it inadvertenly changed things so that we always get exit code 0 even when the command fails, which is quite sad. So just return an anyhow::Error from InitCmd::run()

near#5967 refactored things so that
the init command wouldn't panic on normal/expected errors, but it
inadvertenly changed things so that we always get exit code 0 even
when the command fails, which is quite sad. So just return an `anyhow::Error`
from `InitCmd::run()`
@marcelo-gonzalez marcelo-gonzalez requested a review from a team as a code owner January 11, 2023 17:41
Copy link
Contributor
@jakmeier jakmeier left a comment

Choose a reason for hiding this comment

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

Yeah makes sense to me.

@near-bulldozer near-bulldozer bot merged commit 400e12e into near:master Jan 11, 2023
marcelo-gonzalez added a commit to marcelo-gonzalez/nearcore that referenced this pull request Jan 26, 2023
near#5967 refactored things so that the init command wouldn't panic on normal/expected errors, but it inadvertenly changed things so that we always get exit code 0 even when the command fails, which is quite sad. So just return an `anyhow::Error` from `InitCmd::run()`
marcelo-gonzalez added a commit to marcelo-gonzalez/nearcore that referenced this pull request Jan 26, 2023
near#5967 refactored things so that the init command wouldn't panic on normal/expected errors, but it inadvertenly changed things so that we always get exit code 0 even when the command fails, which is quite sad. So just return an `anyhow::Error` from `InitCmd::run()`
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
0