[Merged by Bors] - Use OS file locks in validator client#1958
[Merged by Bors] - Use OS file locks in validator client#1958michaelsproul wants to merge 9 commits intounstablefrom
Conversation
29d0a20 to
f116a53
Compare
|
Confirmed working on macOS |
blacktemplar
left a comment
There was a problem hiding this comment.
Only one small comment/question, otherwise lgtm.
pawanjay176
left a comment
There was a problem hiding this comment.
LGTM! just a minor question
|
Ready for merging IMO. Will test Windows support once that's closer to being supported in the rest of Lighthouse. |
|
I've added a warning about existing keystores and cleaned up the Just planning to test under Docker (on macOS and Linux) as per @ajsutton's recommendation (thanks!) then should be good to go. |
paulhauner
left a comment
There was a problem hiding this comment.
Great! This will make users very happy, I think.
|
OK, tested on Docker Linux and Docker macOS. Hopefully CI succeeds with that typo fixed, so... bors r+ |
## Issue Addressed Closes #1823 ## Proposed Changes * Use OS-level file locking for validator keystores, eliminating problems with lockfiles lingering after ungraceful shutdowns (`SIGKILL`, power outage). I'm using the `fs2` crate because it's cross-platform (unlike `file-lock`), and it seems to have the most downloads on crates.io. * Deprecate + disable `--delete-lockfiles` CLI param, it's no longer necessary * Delete the `validator_dir::Manager`, as it was mostly dead code and was only used in the `validator list` command, which has been rewritten to read the validator definitions YAML instead. ## Additional Info Tested on: - [x] Linux - [x] macOS - [x] Docker Linux - [x] Docker macOS - [ ] Windows
|
Build failed: |
|
I'm feeling optimistic about that fix: bors r+ |
## Issue Addressed Closes #1823 ## Proposed Changes * Use OS-level file locking for validator keystores, eliminating problems with lockfiles lingering after ungraceful shutdowns (`SIGKILL`, power outage). I'm using the `fs2` crate because it's cross-platform (unlike `file-lock`), and it seems to have the most downloads on crates.io. * Deprecate + disable `--delete-lockfiles` CLI param, it's no longer necessary * Delete the `validator_dir::Manager`, as it was mostly dead code and was only used in the `validator list` command, which has been rewritten to read the validator definitions YAML instead. ## Additional Info Tested on: - [x] Linux - [x] macOS - [x] Docker Linux - [x] Docker macOS - [ ] Windows
|
Cancelled the regular build to let Bors handle it |
|
a8b187b looks good to me. |
|
Damn it, Bors crashed :( Time to try again: bors r- |
## Issue Addressed Closes #1823 ## Proposed Changes * Use OS-level file locking for validator keystores, eliminating problems with lockfiles lingering after ungraceful shutdowns (`SIGKILL`, power outage). I'm using the `fs2` crate because it's cross-platform (unlike `file-lock`), and it seems to have the most downloads on crates.io. * Deprecate + disable `--delete-lockfiles` CLI param, it's no longer necessary * Delete the `validator_dir::Manager`, as it was mostly dead code and was only used in the `validator list` command, which has been rewritten to read the validator definitions YAML instead. ## Additional Info Tested on: - [x] Linux - [x] macOS - [x] Docker Linux - [x] Docker macOS - [ ] Windows
|
Pull request successfully merged into unstable. Build succeeded: |
Issue Addressed
Closes #1823
Proposed Changes
SIGKILL, power outage). I'm using thefs2crate because it's cross-platform (unlikefile-lock), and it seems to have the most downloads on crates.io.--delete-lockfilesCLI param, it's no longer necessaryvalidator_dir::Manager, as it was mostly dead code and was only used in thevalidator listcommand, which has been rewritten to read the validator definitions YAML instead.Additional Info
Tested on: