search

graphprotocol / support

Community support for the Hosted Service of The Graph
https://thegraph.com/
10 stars 3 forks source link

Odd behaviour, printing logs out of order, memory corruption characters? #69

Closed jacobrosenthal closed 3 years ago

jacobrosenthal commented 3 years ago

this graph is running currently nicely

Were launching the v05 version of our contract. Very little has changed for our new version, but its failing almost immediately claiming it cannot save one of our entities without an id. Again that code, nor the contract around that has changed at all.

12/22/2020, 9:26:11 PM

error

Subgraph instance failed to run: Mapping aborted at generated/schema.ts, line 89, column 4, with message: Cannot save Planet entity without an ID wasm backtrace: 0: 0x1cf9 - <unknown>!<wasm function 89> 1: 0x2b7f - <unknown>!<wasm function 142> 2: 0x2c8a - <unknown>!<wasm function 144> in handler `handleBlock` at block #13650612 (b1d71add55610e5f42de3d1c83c990e3196511336e992ba63d2aa5510be00135), code: SubgraphSyncingFailure, id: QmVw6CTwiGpGSH1ZWraEJXi8CuBZS7ag8Jmm51sDcfeDWc

12/22/2020, 9:26:11 PM

info

Done processing Ethereum trigger, waiting_ms: 0, handler: handleBlock, total_ms: 42, trigger_type: Block, number: 13650612, hash: 0xb1d7…0135, runtime_host: 1/1, block_hash: 0xb1d71add55610e5f42de3d1c83c990e3196511336e992ba63d2aa5510be00135, block_number: 13650612

12/22/2020, 9:26:11 PM

error

Handler skipped due to execution failure, error: Mapping aborted at generated/schema.ts, line 89, column 4, with message: Cannot save Planet entity without an ID wasm backtrace: 0: 0x1cf9 - <unknown>!<wasm function 89> 1: 0x2b7f - <unknown>!<wasm function 142> 2: 0x2c8a - <unknown>!<wasm function 144> , handler: handleBlock, runtime_host: 1/1, block_hash: 0xb1d71add55610e5f42de3d1c83c990e3196511336e992ba63d2aa5510be00135, block_number: 13650612

12/22/2020, 9:26:11 PM

info

Done processing Ethereum trigger, waiting_ms: 0, handler: handleArrivalQueued, total_ms: 2, trigger_type: Log, address: 0x2c8b…f254, signature: ArrivalQueued(uint256), runtime_host: 1/1, block_hash: 0xb1d71add55610e5f42de3d1c83c990e3196511336e992ba63d2aa5510be00135, block_number: 13650612

12/22/2020, 9:26:11 PM

info

2 triggers found in this block for this subgraph, block_hash: 0xb1d71add55610e5f42de3d1c83c990e3196511336e992ba63d2aa5510be00135, block_number: 13650612

12/22/2020, 9:26:11 PM

info

Done processing Ethereum trigger, waiting_ms: 0, handler: handleBlock, total_ms: 9, trigger_type: Block, number: 13650611, hash: 0x77d0…5e29, runtime_host: 1/1, block_hash: 0x77d0801e7918c8e2fc688fa99c2e83e5d726eea6f6aa7e827302880ea90c5e29, block_number: 13650611

12/22/2020, 9:26:11 PM

info

Applying 2 entity operation(s), block_hash: 0x77d0801e7918c8e2fc688fa99c2e83e5d726eea6f6aa7e827302880ea90c5e29, block_number: 13650611

12/22/2020, 9:26:11 PM

info

1 trigger found in this block for this subgraph, block_hash: 0x77d0801e7918c8e2fc688fa99c2e83e5d726eea6f6aa7e827302880ea90c5e29, block_number: 13650611

12/22/2020, 9:26:11 PM

info

Done processing Ethereum trigger, waiting_ms: 0, handler: handleBlock, total_ms: 8, trigger_type: Block, number: 13650610, hash: 0x03e6…e942, runtime_host: 1/1, block_hash: 0x03e6e62b0cca5f90682fedb56ac88668bcbdd04d13853660cec45b1c8751e942, block_number: 13650610

presumably this line or this one

But that makes literally no sense.

So in desperation just blasting logging in there logs print out of order? and now I get this error that looks like some kind of memory corruption?

Subgraph instance failed to run: Failed to process trigger: Could not find ABI for contract "慐懐ract", try adding it to the 'abis' section of the subgraph manifest wasm backtrace: 0: 0x16d5 - <unknown>!<wasm function 53> 1: 0x17ff - <unknown>!<wasm function 56> 2: 0x1c3d - <unknown>!<wasm function 90> 3: 0x2a7a - <unknown>!<wasm function 136> 4: 0x2b4c - <unknown>!<wasm function 138> , code: SubgraphSyncingFailure, id: QmdcKKHNTefnf6V5KjRToF26BSKX6k5bTvYFdoN7SK8a18

12/23/2020, 12:10:34 AM

error

uu , data_source: Contract, runtime_host: 1/1, block_hash: 0xb1d71add55610e5f42de3d1c83c990e3196511336e992ba63d2aa5510be00135, block_number: 13650612

12/23/2020, 12:10:34 AM

error

nn , data_source: Contract, runtime_host: 1/1, block_hash: 0xb1d71add55610e5f42de3d1c83c990e3196511336e992ba63d2aa5510be00135, block_number: 13650612

12/23/2020, 12:10:34 AM

error

oo , data_source: Contract, runtime_host: 1/1, block_hash: 0xb1d71add55610e5f42de3d1c83c990e3196511336e992ba63d2aa5510be00135, block_number: 13650612

12/23/2020, 12:10:34 AM

error

pp , data_source: Contract, runtime_host: 1/1, block_hash: 0xb1d71add55610e5f42de3d1c83c990e3196511336e992ba63d2aa5510be00135, block_number: 13650612

12/23/2020, 12:10:34 AM

error

qq , data_source: Contract, runtime_host: 1/1, block_hash: 0xb1d71add55610e5f42de3d1c83c990e3196511336e992ba63d2aa5510be00135, block_number: 13650612

12/23/2020, 12:10:34 AM

error

rr , data_source: Contract, runtime_host: 1/1, block_hash: 0xb1d71add55610e5f42de3d1c83c990e3196511336e992ba63d2aa5510be00135, block_number: 13650612

12/23/2020, 12:10:34 AM

error

tt , data_source: Contract, runtime_host: 1/1, block_hash: 0xb1d71add55610e5f42de3d1c83c990e3196511336e992ba63d2aa5510be00135, block_number: 13650612

12/23/2020, 12:10:34 AM

error

mm , data_source: Contract, runtime_host: 1/1, block_hash: 0xb1d71add55610e5f42de3d1c83c990e3196511336e992ba63d2aa5510be00135, block_number: 13650612
jacobrosenthal commented 3 years ago

Sigh. Logs out of order Im not sure, but I figured out the abi. User error.

I had hardcoded the contract address in Contract.bind in blockhandler because Im not sure if its otherwise available there? And that went out of sync with the subgraph.yaml