Skip to content

Conversation

@rach-id
Copy link
Member

@rach-id rach-id commented Oct 6, 2025

Overview

Closes #5933

This probably should only be merged after we release v6 to mainnet.

evan-forbes
evan-forbes previously approved these changes Oct 6, 2025
rootulp
rootulp previously approved these changes Oct 6, 2025
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.
Copy link
Collaborator

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.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good idea: 81c1a2c

@rach-id rach-id dismissed stale reviews from rootulp and evan-forbes via c0fe944 October 6, 2025 17:07
rootulp
rootulp previously approved these changes Oct 6, 2025
Copy link
Collaborator

@rootulp rootulp left a 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.

@rootulp rootulp self-requested a review October 6, 2025 17:24
… into rachid/chore/cpu-features-check

# Conflicts:
#	cmd/celestia-appd/cmd/cpu_features.go
@rach-id
Copy link
Member Author

rach-id commented Oct 7, 2025

was pushing to the wrong branch 🤦

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Check GFNI | SHA_NI support on node startup

3 participants