Repository navigation
feat: add functions to build attestations and blocks - #30
Merged
Merged
Conversation
MegaRedHand
marked this pull request as ready for review
January 16, 2026 15:06
MegaRedHand
pushed a commit
that referenced
this pull request
Apr 21, 2026
… PR #30 (#312) ## Motivation Implements the `lean_attestations_production_time_seconds` histogram defined in [leanEthereum/leanMetrics#30](leanEthereum/leanMetrics#30), which measures the end-to-end time a node spends producing attestations for all its validators in a given slot. ## Description ### New Metric | Metric | Type | Buckets | Sample collection event | |--------|------|---------|-------------------------| | `lean_attestations_production_time_seconds` | Histogram | 0.01, 0.025, 0.05, 0.1, 0.25, 0.5, 0.75, 1 | On attestation production | ### Implementation - **`crates/blockchain/src/metrics.rs`**: registers the histogram under the `Validator Metrics` family and exposes `time_attestations_production()`, which returns a `TimingGuard` that observes the duration on drop. Added to the `init()` eager-registration list so the metric appears on `/metrics` from process start. - **`crates/blockchain/src/lib.rs`**: instruments `produce_attestations()` with `let _timing = metrics::time_attestations_production();` at the top of the function, capturing the full flow: 1. Attestation data construction (`store::produce_attestation_data`) 2. Per-validator signing 3. Self-delivery via `on_gossip_attestation` 4. Gossip publish ### Documentation - **`docs/metrics.md`**: adds a `Buckets` column to the Validator Metrics table (consistent with the other tables in the doc) and lists the new metric alongside `lean_validators_count` and `lean_is_aggregator`. ## How to Test 1. `make fmt` - passes 2. `make lint` - passes (clippy clean) 3. `make test` - passes 4. Run a local devnet and verify the metric appears on the `/metrics` endpoint (port 5054): ``` curl -s localhost:5054/metrics | grep lean_attestations_production_time_seconds ``` You should see the histogram buckets populate as the node produces attestations each slot. ## Related - leanMetrics spec: leanEthereum/leanMetrics#30 - Previous metrics PR: #289 (Devnet-4 metrics from leanMetrics PR #29)
tcoratger
pushed a commit
to tcoratger/ethlambda
that referenced
this pull request
Oct 30, 2026
The smoke step sat in `Test (node)` on the assumption that the test build had already linked the binary. It had not: `cargo test` never links the plain `ethlambda` binary, and it unifies dev-dependency features in (`bin/ethlambda` enables tokio's `test-util`), which `cargo run` leaves out. tokio is the only crate whose features differ, but everything above it is rebuilt with it: libp2p, hyper, axum, the ethrex crates and the node crates, six minutes of compilation into a target dir the test build leaves at about 1.8 GB free. That pushes the runner to a full disk, so whether `Test (node)` passes comes down to whether the rust-cache post step still finds room to write its log. It fails with `No space left on device` after every test has passed, as on PR lambdaclass#24 and feat/validator-client. A dedicated job builds only the binary's own graph on a fresh runner. It needs no leanSpec fixtures: with `--mock-crypto` the synthetic benchmark generates its own chain and reads no files.
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
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.