blockchain: allow optimistic block insertion in blockchain #12535
client-build.yml
on: pull_request
test client docker file
2m 36s
test-client-cli
3m 18s
Matrix: test-client
Annotations
10 errors and 3 warnings
Unhandled error:
packages/client/src/service/skeleton.ts#L1384
Error: Invalid fcUed optimistic block by number lookup
❯ DBManager.getBlock ../blockchain/src/db/manager.ts:119:17
❯ Skeleton.getBlock src/service/skeleton.ts:1384:44
❯ Skeleton.fillCanonicalChain src/service/skeleton.ts:1205:32
This error originated in "test/sync/skeleton.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "should fill the canonical chain after being linked to genesis". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
Unhandled error:
packages/client/src/service/skeleton.ts#L1384
Error: Invalid fcUed optimistic block by number lookup
❯ DBManager.getBlock ../blockchain/src/db/manager.ts:119:17
❯ Skeleton.getBlock src/service/skeleton.ts:1384:44
❯ Skeleton.fillCanonicalChain src/service/skeleton.ts:1205:32
This error originated in "test/sync/skeleton.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "should fill the canonical chain after being linked to a canonical block past genesis". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
Unhandled error:
packages/client/src/service/skeleton.ts#L1384
Error: Invalid fcUed optimistic block by number lookup
❯ DBManager.getBlock ../blockchain/src/db/manager.ts:119:17
❯ Skeleton.getBlock src/service/skeleton.ts:1384:44
❯ Skeleton.fillCanonicalChain src/service/skeleton.ts:1205:32
This error originated in "test/sync/skeleton.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
The latest test that might've caused the error is "should abort filling the canonical chain if the terminal block is invalid". It might mean one of the following:
- The error was thrown, while Vitest was running this test.
- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
|
test/sync/beaconsync.spec.ts > [BeaconSynchronizer] > should extend and set with a valid head:
packages/client/src/sync/beaconsync.ts#L92
Error: A base fee for a block can only be set with EIP1559 being activated
❯ new BlockHeader ../block/src/header/header.ts:183:13
❯ createBlockHeader ../block/src/header/constructors.ts:17:10
❯ Module.createBlockHeaderFromBytesArray ../block/src/header/constructors.ts:30:18
❯ DBManager.getHeader ../blockchain/src/db/manager.ts:190:12
❯ DBManager.getBlock ../blockchain/src/db/manager.ts:133:20
❯ BeaconSynchronizer.open src/sync/beaconsync.ts:92:25
❯ test/sync/beaconsync.spec.ts:229:5
|
test/sync/skeleton.spec.ts > [Skeleton] / initSync > A single leftover subchain is present and the new head is extending:
packages/client/src/service/skeleton.ts#L1384
Error: Invalid fcUed optimistic block by number lookup
❯ DBManager.getBlock ../blockchain/src/db/manager.ts:119:17
❯ Skeleton.getBlock src/service/skeleton.ts:1384:44
❯ Skeleton.processNewHead src/service/skeleton.ts:362:31
❯ src/service/skeleton.ts:441:32
❯ Skeleton.runWithLock src/service/skeleton.ts:161:27
❯ test/sync/skeleton.spec.ts:247:7
|
test/sync/skeleton.spec.ts > [Skeleton] / initSync > Duplicate announcement should not modify subchain:
packages/client/src/service/skeleton.ts#L1384
Error: Invalid fcUed optimistic block by number lookup
❯ DBManager.getBlock ../blockchain/src/db/manager.ts:119:17
❯ Skeleton.getBlock src/service/skeleton.ts:1384:44
❯ Skeleton.processNewHead src/service/skeleton.ts:319:40
❯ src/service/skeleton.ts:441:32
❯ Skeleton.runWithLock src/service/skeleton.ts:161:27
❯ test/sync/skeleton.spec.ts:247:7
|
test/sync/skeleton.spec.ts > [Skeleton] / initSync > A new alternate head is announced in the middle should truncate subchain:
packages/client/src/service/skeleton.ts#L1384
Error: Invalid fcUed optimistic block by number lookup
❯ DBManager.getBlock ../blockchain/src/db/manager.ts:119:17
❯ Skeleton.getBlock src/service/skeleton.ts:1384:44
❯ Skeleton.processNewHead src/service/skeleton.ts:319:40
❯ src/service/skeleton.ts:441:32
❯ Skeleton.runWithLock src/service/skeleton.ts:161:27
❯ test/sync/skeleton.spec.ts:247:7
|
test/sync/skeleton.spec.ts > [Skeleton] / initSync > The old subchains to be truncated/cleared and a new chain be created for the dangling head:
packages/client/src/service/skeleton.ts#L1384
Error: Invalid fcUed optimistic block by number lookup
❯ DBManager.getBlock ../blockchain/src/db/manager.ts:119:17
❯ Skeleton.getBlock src/service/skeleton.ts:1384:44
❯ Skeleton.processNewHead src/service/skeleton.ts:319:40
❯ src/service/skeleton.ts:441:32
❯ Skeleton.runWithLock src/service/skeleton.ts:161:27
❯ test/sync/skeleton.spec.ts:247:7
|
test/sync/skeleton.spec.ts > [Skeleton] / setHead > Initialize a sync and try to extend it with a subsequent block:
packages/client/test/sync/skeleton.spec.ts#L375
AssertionError: test 0: received wrong error expected=undefined actual=Invalid fcUed optimistic block by number lookup
❯ test/sync/skeleton.spec.ts:375:18
|
test/sync/skeleton.spec.ts > [Skeleton] / setHead > Initialize a sync and try to extend it with the existing head block:
packages/client/test/sync/skeleton.spec.ts#L375
AssertionError: test 1: received wrong error expected=undefined actual=Invalid fcUed optimistic block by number lookup
❯ test/sync/skeleton.spec.ts:375:18
|
test client docker file
The following actions uses node12 which is deprecated and will be forced to run on node16: docker/setup-qemu-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
test client docker file
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/setup-qemu-action@v1, docker/setup-buildx-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
test client docker file
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|