Do not panic if the `fdlimit` call to increase the file descriptor limit fails (#2155)
# 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.
# Checklist
- [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>
parent
490fb665
Branches
Pipeline
#415004
canceled
with stages
in
5 minutes and 49 seconds
Stage:
Stage:
Stage:
Stage:
Stage:
Stage:
Showing
- Cargo.lock 7 additions, 6 deletionsCargo.lock
- substrate/client/cli/Cargo.toml 1 addition, 1 deletionsubstrate/client/cli/Cargo.toml
- substrate/client/cli/src/config.rs 17 additions, 6 deletionssubstrate/client/cli/src/config.rs
- substrate/client/service/test/Cargo.toml 1 addition, 1 deletionsubstrate/client/service/test/Cargo.toml
- substrate/client/service/test/src/lib.rs 1 addition, 1 deletionsubstrate/client/service/test/src/lib.rs
Please register or sign in to comment