bug(test-cli-consume): fix bpos in hive ruleset #1758
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🗒️ Description
Enables BPO configs for forks that occur after them such as Amsterdam. This aims to fix the blob related tests on the most recent BAL run on Hive CI: https://hive.ethpandaops.io/#/group/bal
As Amsterdam is based on top of Osaka within
forks.py, the BPO hive variables are not included. This leads to chain spec issues for EL clients due to there ordering of forks, when all the timestamps are set to 0. This PR fixes the latter.Additionally adds BPO5 and a transition fork from BPO5 to Amsterdam. This goes off of the assumption that we will have 5 BPOs on Osaka mainnet which is currently planned. Note BPO5 is added here for chain spec issues in EL clients.
🔗 Related Issues or PRs
N/A.
✅ Checklist
toxchecks to avoid unnecessary CI fails, see also Code Standards and Enabling Pre-commit Checks:uvx tox -e statictype(scope):.