-
Notifications
You must be signed in to change notification settings - Fork 324
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore!: enable multiple L1 nodes to be used (#11945)
- Updates `ETHEREUM_HOST` env var to `ETHEREUM_HOSTS`. Using a single host should still work as it did before - Single `ViemWalletClient` & `ViemPublicClient` BREAKING CHANGE: - env var `ETHEREUM_HOST` -> `ETHEREUM_HOSTS` - CLI arg `--l1-rpc-url` -> `--l1-rpc-urls` - TypeScript configs with `l1RpcUrl` -> `l1RpcUrls` - aztec.js functions with `l1RpcUrl` -> `l1RpcUrls` - `DeployL1Contracts` (type) -> `DeployL1ContractsReturnType` Fixes #11790 Follow-up #12254
- Loading branch information
Showing
173 changed files
with
1,382 additions
and
1,488 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
fcf6278
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.
Possible performance regression was detected for benchmark 'P2P Testbench'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold
1.05
.degree-1-strict - minDelay
950
ms113
ms8.41
degree-1-strict - maxDelay
950
ms540
ms1.76
degree-1-strict - averageDelay
950
ms350.75
ms2.71
degree-1-strict - medianDelay
950
ms434
ms2.19
normal-degree-100-nodes - minDelay
251
ms175
ms1.43
normal-degree-100-nodes - maxDelay
6471
ms482
ms13.43
normal-degree-100-nodes - averageDelay
998.8
ms333.9
ms2.99
normal-degree-100-nodes - medianDelay
476
ms375
ms1.27
normal-degree-50-nodes - minDelay
275
ms210
ms1.31
normal-degree-50-nodes - maxDelay
7017
ms6255
ms1.12
This comment was automatically generated by workflow using github-action-benchmark.
CC: @Maddiaa0