-
Notifications
You must be signed in to change notification settings - Fork 480
chore: add CPU features check during install and start of celestia-appd #5969
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
base: main
Are you sure you want to change the base?
chore: add CPU features check during install and start of celestia-appd #5969
Conversation
| If you are running this node in production, consider upgrading to a CPU with these features. | ||
|
|
||
| This node will continue to run, but may experience reduced performance for cryptographic operations. | ||
| If you need to bypass this check, use the --testing-environment flag. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[uber nit][not blocking] --testing-environment sounds like it could disable multiple checks like:
- this CPU check
- bbr
- override the default block time from 6 seconds to 1 second
if this check only overrides the CPU requirement, maybe it could be renamed to something more specific. For bbr we have --force-no-bbr so maybe --force-no-new-cpu.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good idea: 81c1a2c
Co-authored-by: Rootul P <[email protected]>
Co-authored-by: Rootul P <[email protected]>
Co-authored-by: Rootul P <[email protected]>
Co-authored-by: Rootul P <[email protected]>
Co-authored-by: Rootul P <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops looks like the --testing-environment flag is still present on the most recent commit so the rename still needs to update a few more instances.
… into rachid/chore/cpu-features-check # Conflicts: # cmd/celestia-appd/cmd/cpu_features.go
|
was pushing to the wrong branch 🤦 |
Overview
Closes #5933
This probably should only be merged after we release v6 to mainnet.