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

Do not panic if the fdlimit call to increase the file descriptor limit fails (cherrypicked) #9

Merged
merged 1 commit into from
Dec 1, 2023

Conversation

ParthDesai
Copy link

@ParthDesai ParthDesai commented Dec 1, 2023

This PR contains commit cherry-picked paritytech@079b14f from upstream. The description below is copied from the PR as is.

Description

Sometimes changing file descriptor limits is not allowed, but there is no need to crash the node if/when this happens. Since fdlimit's author decided to use panics instead of returning Result, we need to catch it.

  • My PR includes a detailed description as outlined in the "Description" section above
  • My PR follows the labeling requirements of this project (at minimum one label for T
    required)
  • I have made corresponding changes to the documentation (if applicable)
  • I have added tests that prove my fix is effective or that my feature works (if applicable)

…mit fails (paritytech#2155)

Sometimes changing file descriptor limits is not allowed, but there is
no need to crash the node if/when this happens. Since `fdlimit`'s author
decided to use panics instead of returning `Result`, we need to catch
it.

- [x] My PR includes a detailed description as outlined in the
"Description" section above
- [ ] My PR follows the [labeling requirements](CONTRIBUTING.md#Process)
of this project (at minimum one label for `T`
  required)
- [ ] I have made corresponding changes to the documentation (if
applicable)
- [ ] I have added tests that prove my fix is effective or that my
feature works (if applicable)

---------

Co-authored-by: Koute <koute@users.noreply.github.com>
@ParthDesai ParthDesai merged commit c63a8b2 into subspace-v1 Dec 1, 2023
2 of 6 checks passed
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