mirror of
https://github.com/sigp/lighthouse.git
synced 2026-04-20 14:28:37 +00:00
Markdown linter (#5494)
* linter * Add markdown linter * add env * only check markdown * Add token * Update .github/workflows/test-suite.yml * Markdown linter * Exit code * Update script * rename * mdlint * Add an empty line after end of file * Testing disable * add text * update mdlint.sh * ori validator inclusion * Add config yml file * Remove MD041 and fix advanced-datadir file * FIx validator inclusion file conflict * Merge branch 'unstable' into markdown-linter * change files * Merge branch 'markdown-linter' of https://github.com/chong-he/lighthouse into markdown-linter * mdlint * Remove MD025 * Remove MD036 * Remove MD045 * Removr MD001 * Set MD028 to false * Remove MD024 * Remove MD055 * Remove MD029 * Remove MD040 * Set MD040 to false * Set MD033 to false * Set MD013 to false * Rearrange yml file * Update mdlint.sh and test * Test remove fix * Test with fix * Test with space * Fix summary indentation * Test mdlint.sh * Update mdlint.sh * Test * Update * Test fix * Test again * Fix * merge into check-code * Update scripts/mdlint.sh Co-authored-by: Mac L <mjladson@pm.me> * Update scripts/mdlint.sh Co-authored-by: Mac L <mjladson@pm.me> * Remove set -e * Add comment * Merge pull request #7 from chong-he/unstable Merge unstable to markdown branch * mdlint * Merge branch 'unstable' into markdown-linter * mdlint
This commit is contained in:
@@ -100,7 +100,7 @@ lighthouse \
|
||||
> it is recommended for an additional layer of safety. It will result in 2-3
|
||||
> epochs of downtime for the validator after it is moved, which is generally an
|
||||
> inconsequential cost in lost rewards or penalties.
|
||||
>
|
||||
>
|
||||
> Optionally, users can add the `--http-store-passwords-in-secrets-dir` flag if they'd like to have
|
||||
> the import validator keystore passwords stored in separate files rather than in the
|
||||
> `validator-definitions.yml` file. If you don't know what this means, you can safely omit the flag.
|
||||
@@ -158,7 +158,9 @@ Moved keystore 1 of 2
|
||||
Moved keystore 2 of 2
|
||||
Done.
|
||||
```
|
||||
|
||||
At the same time, `lighthouse vc` will log:
|
||||
|
||||
```bash
|
||||
INFO Importing keystores via standard HTTP API, count: 1
|
||||
INFO Enabled validator voting_pubkey: 0xab6e29f1b98fedfca878edce2b471f1b5ee58ee4c3bd216201f98254ef6f6eac40a53d74c8b7da54f51d3e85cacae92f, signing_method: local_keystore
|
||||
@@ -183,12 +185,13 @@ lighthouse \
|
||||
```
|
||||
|
||||
> Note: If you have the `validator-monitor-auto` turned on, the source beacon node may still be reporting the attestation status of the validators that have been moved:
|
||||
|
||||
```
|
||||
INFO Previous epoch attestation(s) success validators: ["validator_index"], epoch: 100000, service: val_mon, service: beacon
|
||||
```
|
||||
> This is fine as the validator monitor does not know that the validators have been moved (it *does not* mean that the validators have attested twice for the same slot). A restart of the beacon node will resolve this.
|
||||
|
||||
> This is fine as the validator monitor does not know that the validators have been moved (it *does not* mean that the validators have attested twice for the same slot). A restart of the beacon node will resolve this.
|
||||
|
||||
Any errors encountered during the operation should include information on how to
|
||||
proceed. Assistance is also available on our
|
||||
[Discord](https://discord.gg/cyAszAh).
|
||||
[Discord](https://discord.gg/cyAszAh).
|
||||
|
||||
Reference in New Issue
Block a user