Update with upstream #12
Open
Conversation
This file contains hidden or 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
…aops#760) This will enable additional peer infos (ENR/Enode, etc.) to be shown on the client pages. Implemented in ethpandaops/dora#117
…pandaops#761) Related to the deprecation of the gRPC gateway: OffchainLabs/prysm#14089 Currently the `mix-with-tools.yaml` test was failing due to the keymanager being enabled: ``` == FINISHED SERVICE 'vc-2-nethermind-prysm' LOGS =================================== Caused by: An error occurred while waiting for all TCP and UDP ports to be open Caused by: Unsuccessful ports check for IP '172.16.0.34' and port spec '{privatePortSpec:0xc00091a0c0}', even after '240' retries with '500' milliseconds in between retries. Timeout '2m0s' has been reached Caused by: An error occurred while calling network address '172.16.0.34:5056' with port protocol 'TCP' and using time out '200ms' Caused by: dial tcp 172.16.0.34:5056: connect: connection refused Error encountered running Starlark code. ```
update the built int validator-lifecycle-test for assertoor
Currently `'*'` is passed to Teku, which is not correct, so I see `Not Authorized` when trying to access Teku metrics, Prometheus says that Teku is down because of 403, and Grafana metrics are empty. Only `*` should be passed, which is the purpose of the fix. I don't know how to test it, so not 100% on the fix.
🤖 I have created a release *beep* *boop* --- ## [4.3.0](ethpandaops/ethereum-package@4.2.0...4.3.0) (2024-09-23) ### Features * add prefunded accounts ([ethpandaops#752](ethpandaops#752)) ([1be7efa](ethpandaops@1be7efa)) * dora - show more infos about all peers on client pages ([ethpandaops#760](ethpandaops#760)) ([c77d95f](ethpandaops@c77d95f)) ### Bug Fixes * `metrics-host-allowlist` for Teku ([ethpandaops#765](ethpandaops#765)) ([ad75fcc](ethpandaops@ad75fcc)) * built in validator lifecycle test for assertoor ([ethpandaops#763](ethpandaops#763)) ([6f868cc](ethpandaops@6f868cc)) * explicitly set client contexts ([ethpandaops#755](ethpandaops#755)) ([94dc531](ethpandaops@94dc531)) * no default resource limits ([ethpandaops#768](ethpandaops#768)) ([4c4831b](ethpandaops@4c4831b)) * prysm gRPC removal - use http server instead for keymanager ([ethpandaops#761](ethpandaops#761)) ([ba91174](ethpandaops@ba91174)) * remove epoch checker for goomy ([ethpandaops#754](ethpandaops#754)) ([f124bbf](ethpandaops@f124bbf)) * remove exp RPC API namespace flag from nimbus-eth1 configuration ([ethpandaops#767](ethpandaops#767)) ([8fec454](ethpandaops@8fec454)) * reth-builder volume claim ([ethpandaops#771](ethpandaops#771)) ([4570328](ethpandaops@4570328)) * update dora config for latest release & remove custom images ([ethpandaops#748](ethpandaops#748)) ([a433c50](ethpandaops@a433c50)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
…ops#773) Please note: `grafana_additional_dashboards` -> `grafana_params.additional_dashboards`
this adds the database section to the assertoor config. assertoor falls back to an in memory database if the database section is left out. however, the in memory database caused issues with dora earlier, so it's better to use a non persistent file.
update built in assertoor tests for compatibility with recent assertoor changes: * add unique id to all tests
Think the prometheus_grafana services are off by default, since I had to modify the config this way to get grafana and prometheus to start. Signed-off-by: Samuel Laferriere <[email protected]>
Currently the 6.7.2 introduced reth support.
Even tho the workaround (below) is still in the code, it fixes some
indexing issue. (Specifically something with the transaction receipts
decoding).
Still active (and if removed, still not working) workaround:
```
"ETHEREUM_JSONRPC_VARIANT": "erigon"
if el_client_name == "erigon" or el_client_name == "reth"
else el_client_name,
```
Co-authored-by: Keszey Dániel <[email protected]>
…aops#792) As per issue in blockscout, [here](blockscout/blockscout#10869 (comment)) is the solution which solved the verification problem. PS: Also bumped the blockscout version itself. (Tested.) Signed-off-by: D <[email protected]> Co-authored-by: Keszey Dániel <[email protected]>
This PeerDAS metrics dashboard is implemented according to the current PeerDAS metrics specs. It can be used by all the CL clients which implemented the set of [these metrics](ethereum/beacon-metrics#13). The metrics are still under discussion, so, the dashboard is currently in development. Filters: by client, job, supernode.
…ps#791) Adds the `use_remote_signer` flag, outsourcing validator key management to a remote signer, which validator clients connect to. Supported by all VCs except Lighthouse through this PR. Slashing protection DB is not enabled for web3signer since that would require adding significantly more complexity - creating a separate postgres DB and running migrations. I was thinking a lot what to call the remote signer service, in the end went with `signer-1-geth-lodestar` (this is the remote signer for `vc-1-geth-lodestar`). Addresses ethpandaops#263 / ethpandaops#758 Prerequisite for adding [Vero](https://github.com/serenita-org/vero) as a validator client - it exclusively uses a remote signer --------- Co-authored-by: Barnabas Busa <[email protected]>
The default image: `gcr.io/prysmaticlabs/prysm/beacon-chain:latest` already has the `http-` flags as per OffchainLabs/prysm#14089 I also swapped the ports. Instead of using 3500 for the HTTP server and 4000 for the RPC server ( which is actually prysm's default behaviour). The problem is that all the other CL clients are running their HTTP beacon API under port 4000 ( `BEACON_HTTP_PORT_NUM= 4000`) . So I think it makes sense to do the same for prysm here.
Signed-off-by: Barnabas Busa <[email protected]>
Signed-off-by: Barnabas Busa <[email protected]>
…s#855) `electra-support` as been merged into master and a new release is available too.
…is active (ethpandaops#858) Signed-off-by: Barnabas Busa <[email protected]>
This PR replaces [goomy](https://github.com/ethpandaops/goomy-blob) with [spamoor](https://github.com/ethpandaops/spamoor). The spamoor project is based on goomy, but was improved a lot to handle high transaction throughput reliably. It supports all features that goomy provides, but blob scenarios are prefixed with `blob-`. As spamoor works much better by now, it makes sense to deprecate goomy and replace it with spamoor.
ethpandaops#862) Co-authored-by: pk910 <[email protected]> Co-authored-by: pk910 <[email protected]>
It was missing a leading 0.
This PR elaborates what the `snooper_elabed` flag does.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.