Skip to content

[Bug]: Network subgraph erroring out and stopped indexing #10

@tmigone

Description

@tmigone

Indexer address

Operator address

Indexer agent version

Indexer service version

TAP agent version

Description

After accepting a dispute on the legacy dispute manager:

Subgraph instance failed to run: transaction 1ec1d7135f9207b6eb2565d91eeae4647f39cac3dbfb07785dd3d3e37e5845bb: error while executing at wasm backtrace:	    0:   0x72cd - <unknown>!~lib/@graphprotocol/graph-ts/chain/ethereum/ethereum.SmartContract#call	    1:   0x741f - <unknown>!src/mappings/staking/handleStakeSlashed: Mapping aborted at ~lib/@graphprotocol/graph-ts/chain/ethereum.ts, line 683, column 7, with message: Call reverted, probably because an `assert` or `require` in the contract failed, consider using `try_stakes` to handle this in the mapping. in handler `handleStakeSlashed` at block #211453697 (1448e3c4debf2547237bf3633c0796195625040d23c7ab32ed4420fc626be5c7), code: SubgraphSyncingFailure, runner_index: 717

Relevant Logs

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions