Skip to content

fix(db): use ru height for history indices & events instead of using the host block number #80

fix(db): use ru height for history indices & events instead of using the host block number

fix(db): use ru height for history indices & events instead of using the host block number #80

Triggered via pull request August 13, 2025 15:44
Status Success
Total duration 5m 8s
Artifacts

rust.yml

on: pull_request
rust-library-base  /  ...  /  Test Suite
4m 32s
rust-library-base / Base Checks / Test Suite
rust-library-base  /  ...  /  doctest
4m 19s
rust-library-base / Base Checks / doctest
rust-library-base  /  ...  /  Rustfmt
45s
rust-library-base / Base Checks / Rustfmt
rust-library-base  /  ...  /  Clippy
3m 29s
rust-library-base / Base Checks / Clippy
rust-library-base  /  ...  /  Docs
3m 21s
rust-library-base / Base Checks / Docs
rust-library-base  /  Feature Checks
3m 44s
rust-library-base / Feature Checks
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
rust-library-base / Base Checks / Rustfmt
Cache not found for keys: v0-rust-rustfmt-Linux-arm64-ab4dd511-fcdaf8f3, v0-rust-rustfmt-Linux-arm64-ab4dd511
rust-library-base / Base Checks / Docs
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
rust-library-base / Base Checks / Docs
Cache not found for keys: v0-rust-docs-Linux-arm64-ab4dd511-fcdaf8f3, v0-rust-docs-Linux-arm64-ab4dd511