Skip to content

Use aligned block ranges in eth_getLogs requests during historical processing #1268

Use aligned block ranges in eth_getLogs requests during historical processing

Use aligned block ranges in eth_getLogs requests during historical processing #1268

Triggered via pull request August 5, 2024 11:19
Status Success
Total duration 2m 7s
Artifacts

on-pr.yaml

on: pull_request
Matrix: lint
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
lint (18.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
lint (18.x)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (18.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (18.x)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/