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

Exit on panics, rather than unwinding #3177

Merged
merged 1 commit into from
Oct 28, 2024
Merged

Exit on panics, rather than unwinding #3177

merged 1 commit into from
Oct 28, 2024

Conversation

teor2345
Copy link
Member

@teor2345 teor2345 commented Oct 28, 2024

This PR makes the node, farmer, gateway, and boostrap node exit immediately when there is a panic.

Previously, the Rust panic handler would unwind the stack, and drop the tokio runtime. This could lead to a hang if tasks were deadlocked, livelocked, or otherwise running forever without yielding.

Close #3175.

Code contributor checklist:

@teor2345 teor2345 added this pull request to the merge queue Oct 28, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Oct 28, 2024
@nazar-pc nazar-pc added this pull request to the merge queue Oct 28, 2024
Merged via the queue into main with commit e09387b Oct 28, 2024
8 checks passed
@nazar-pc nazar-pc deleted the exit-on-panic branch October 28, 2024 14:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Node hangs when started on broken network, after worker tries to shut down
2 participants