Pin rust_eth_kzg to 0.5.1#6608
Conversation
|
Benchmarks for |
|
Context initialisation is 33% faster with 0.5.1: |
|
@mergify queue |
🛑 The pull request has been removed from the queue
|
|
@mergify requeue |
✅ This pull request will be re-embarked automaticallyDetailsThe followup |
🛑 The pull request has been removed from the queue
|
|
@mergify requeue |
✅ This pull request will be re-embarked automaticallyDetailsThe followup |
✅ The pull request has been merged automaticallyDetailsThe pull request has been merged automatically at 720f596 |
Update cargo dependencies while keeping `rust_eth_kzg` pinned to `0.5.1` due to the regression described in: - #6608 The changes from that PR were not sufficient to actually pin the dependencies of `rust_eth_kzg`, because the dependencies from the workspace Cargo.toml file were not being used anywhere. To fix this, I've added them as explicit dependencies in `crypto/kzg/Cargo.toml`. With this change, `cargo update` no longer tries to update them.
Proposed Changes
Temporarily pin
rust_eth_kzgto 0.5.1 as 0.5.2 seems to have regressed some loading performance enough for our CI to start timing out in the simulator tests (32s timeout). See: