CallParser assertion failure "missing required event" on Westend Asset Hub runtime westmint@1022000

[claravanstaden]

Describe the bug
CallParser.next() at parser.ts:319 crashes with AssertionError: missing required event when processing blocks on Westend Asset Hub after runtime upgrade to westmint@1022000. The parser expects a System.ExtrinsicSuccess or System.ExtrinsicFailed event for every extrinsic, but some extrinsics in the new runtime don't have one. This is not limited to a single block — multiple blocks in this runtime are affected.

To Reproduce
Steps to reproduce the behavior:

1. Create a substrate processor targeting asset-hub-westend with .addEvent() and extrinsic: true
2. Process blocks from 13636575 onwards
3. Processor crashes at block 13636580

Expected behavior
The processor should handle extrinsics without System.ExtrinsicSuccess/System.ExtrinsicFailed events gracefully instead of crashing.

Environment:

• @subsquid/substrate-processor: 8.6.1
• @subsquid/substrate-data: 4.4.4
• Node.js: 22
• OS: Ubuntu (Subsquid Cloud)

Applicable to decoding issues:

• Chain: asset-hub-westend
• Spec version: 1022000
• Block: 13636580
• Block hash: 0xc1b2a5dc66eca211beedfdc13dec0956065ecdd76c403afdd8e24349cc8f60fe
• Endpoint: wss://asset-hub-westend-rpc.n.dwellir.com

Additional context
Workaround — patch @subsquid/substrate-data lib/parsing/call/parser.js:

•        let event = this.next();
  

•        let event = this.maybeNext();
  

•        if (!event) continue;
         switch (event.name) {
  

[alistair-singh]

We are getting this issue in Kusama Asset Hub now.

$ sqd process:kusama:assethub

PROCESS:KUSAMA:ASSETHUB
22:33:20 INFO  sqd:processor processing blocks from 15882267
22:33:21 INFO  sqd:processor using archive data source
22:33:21 INFO  sqd:processor prometheus metrics are served at port 55701
22:33:21 INFO  sqd:processor using chain RPC data source
22:34:29 FATAL sqd:processor AssertionError [ERR_ASSERTION]: missing required event
                                 at assertNotNull (/home/src/snowbridge-subsquid/node_modules/@subsquid/util-internal/src/misc.ts:6:11)
                                 at CallParser.next (/home/src/snowbridge-subsquid/node_modules/@subsquid/substrate-data/src/parsing/call/parser.ts:319:29)
                                 at CallParser.parse (/home/src/snowbridge-subsquid/node_modules/@subsquid/substrate-data/src/parsing/call/parser.ts:83:30)
                                 at parseCalls (/home/src/snowbridge-subsquid/node_modules/@subsquid/substrate-data/src/parsing/call/index.ts:18:7)
                                 at BlockParser.calls (/home/src/snowbridge-subsquid/node_modules/@subsquid/substrate-data/src/parsing/block.ts:119:26)
                                 at BlockParser.value (/home/src/snowbridge-subsquid/node_modules/@subsquid/util-internal/src/def.ts:16:30)
                                 at parseBlock (/home/src/snowbridge-subsquid/node_modules/@subsquid/substrate-data/src/parsing/block.ts:39:26)
                                 at Parser.parseBlock (/home/src/snowbridge-subsquid/node_modules/@subsquid/substrate-data/src/parser.ts:80:45)
                                 at Parser.parse (/home/src/snowbridge-subsquid/node_modules/@subsquid/substrate-data/src/parser.ts:67:28)
                                 at processTicksAndRejections (node:internal/process/task_queues:105:5)
                                 generatedMessage: false
                                 code: ERR_ASSERTION
                                 actual: false
                                 expected: true
                                 operator: ==
                                 blockHeight: 15882269
                                 blockHash: 0x779a870911faa585aac0b258ec56c08abca0486421bde85a549c2e08155249a9

We have tried updating to latest versions of squids.

Versions:

@subsquid/evm-processor       │ ^1.29.1
@subsquid/graphql-server      │ ^4.12.0
@subsquid/substrate-processor │ ^8.7.0
@subsquid/typeorm-migration   │ ^1.3.1
@subsquid/typeorm-store       │ ^1.8.1
@subsquid/evm-typegen         │ ^4.4.0
@subsquid/substrate-typegen   │ ^8.1.0
@subsquid/typeorm-codegen     │ ^2.2.0
@subsquid/cli                 │ ^3.3.5 

[kukabi]

We are also having the same issue as listed by @alistair-singh since yesterday.

[tmcgroul]

the problem is fixed for both kusama and westend asset hub. to apply changes to your indexers please run the following command: rm -rf node_modules package-lock.json && npm i