Failed to process trigger in block

[akme]

After a lot of subgraphs were added, found out some errors for a few of them.

What is the current behavior?

QmSXzWZhbDgDg9YyDeivFqYBc1zxESyBYBH3W9CzmupYQd | Failed to process trigger in block #10802337 (9ee254cca1ae3726a79319b88c10f02002d04597990982f946b1189bfebd1287), transaction acc9d9d5c4168e079be4c47eaf1e28c686efe30dc081073e2a60423413ffebee: Failed to invoke handler 'handleBurnedSynths': Mapping aborted at ~lib/@graphprotocol/graph-ts/chain/ethereum.ts, line 439, column 6, with message: Call reverted, probably because an `assert` or `require` in the contract failed, consider using `try_balanceOf` to handle this in the mapping. wasm backtrace: 0: 0x1bd1 - <unknown>!<wasm function 75> 1: 0x1bf2 - <unknown>!<wasm function 76> 2: 0x21f0 - <unknown>!<wasm function 119> 3: 0x2d58 - <unknown>!<wasm function 149> | -
-- | -- | --
QmWNP1jqMZm61G8FbsLzi9Mnii5qRXbkadBxXVHZPqzKri | Failed to process trigger in block #10693164 (26c8487ab77c86e5d166228ca90016653b316e4a993a7bf6c4e64f9f47a0b60c), transaction 553877cea2c29f6d251ce7ce24588256285c78fac3becc7b64ca64a30b2a1e83: Failed to invoke handler 'handleRedeemed': Mapping aborted at ~lib/@graphprotocol/graph-ts/index.ts, line 1356, column 4, with message: Call reverted, probably because an `assert` or `require` in the contract failed, consider using `try_getBasketManager` to handle this in the mapping. wasm backtrace: 0: 0xfdb - <unknown>!<wasm function 34> 1: 0x102e - <unknown>!<wasm function 37> 2: 0x1956 - <unknown>!<wasm function 85> 3: 0x1a3d - <unknown>!<wasm function 86> 4: 0x1f7c - <unknown>!<wasm function 125> | -
QmNs5fU6VkyGUsaNsa5sUHEKpzCA5AZWKJG8LaBrcCRpmW | Failed to process trigger in block #9663088 (ffe26e8316eff7c71d192925b72d5529828bc115a29b51c25da3d7b143c30894), transaction 0adcf37d5ea87ad72013c09baf073b77477cf65b59b6145845cefd4ade625305: Failed to invoke handler 'handleTokenExchangeUnderlying': Mapping aborted at ~lib/@graphprotocol/graph-ts/index.ts, line 1356, column 4, with message: Call reverted, probably because an `assert` or `require` in the contract failed, consider using `try_getPricePerFullShare` to handle this in the mapping. wasm backtrace: 0: 0x149c - <unknown>!<wasm function 56> 1: 0x24de - <unknown>!<wasm function 152> 2: 0x2637 - <unknown>!<wasm function 155> 3: 0x280a - <unknown>!<wasm function 158> 4: 0x2ee5 - <unknown>!<wasm function 167>

What is the expected behavior?
No errors

[leoyvens]

Please provide more information on why this is unexpected and what are the instructions to reproduce.

[akme]

outdated

[apaul243]

Handler skipped due to execution failure, error: Mapping aborted at ~lib/@graphprotocol/graph-ts/chain/ethereum.ts, line 439, column 6, with message: Call reverted, probably because an assert or require in the contract failed, consider using try_getReserves to handle this in the mapping. wasm backtrace: 0: 0x181f - !~lib/@graphprotocol/graph-ts/chain/ethereum/ethereum.SmartContract#call 1: 0x27fe -

Getting similar error while deploying sushi subgraphs , this try_methodName causing issues...anyone got ideas?

[JamesEarle]

@akme Why is this outdated? Can you please explain what the fix or change is?

[akme]

I don't even remember what the root cause was, but the error has gone, so I marked it as outdated, if you face any issues like this, better open new issue.

[stebansaa]

having the same issues

[chrisckwong821]

having the same issues

[Austin929]

having the same issues

[TheMyth42]

I am having the same issue

Mapping aborted at ~lib/@graphprotocol/graph-ts/chain/ethereum.ts, line 681, column 7, with message: Call reverted, probably because an assert or require in the contract failed, consider using try_admin to handle this in the mapping. wasm backtrace: 0: 0x3440