graphprotocol / mission-control-indexer

Technical indexer documentation and infrastructure templates for the Mission Control testnet
21 stars 4 forks source link

P2 subgraph errors list #169

Open fattox opened 4 years ago

fattox commented 4 years ago

Since the Uniswap V2 indexing issue has been resolved with today's fix, i thought i'd list out what issues (from my POV) still remain with subgraph indexing. (I couldn't fish out an existing issue that mentions all current errors, so apologies if i overlooked it)

This is a fresh DB, syncing all mainnet subgraphs, since the start of P2 launch. The errors i have so far are:

- Name: Known Origin
- Hash: QmTFeK8XKtA6hm2nZ8ectqyqTmx1ga8qiMpxQyyxfBrduv
- Block: 11092535
- Error: Failed to invoke handler 'handleTransfer'
- Name: Livepeer
- Hash: QmaEsTQhqGfZMjHYpNxmcxU3pD4GbAU6u5F8AqePeQumYv

- Block: 10053552
- Error: Failed to invoke handler 'vote'

- Block: 10053060
- Error: Failed to invoke handler 'updatePollTallyOnEarningsClaimed'
- Name: Tellor Dispute V2
- Hash: QmfCaCcQnfBWXgCpbtf9kKWosVqUbeGLfEomYVJkMBqKj9
- Block: 11074853
- Error: Failed to invoke handler 'handleVoted'
- Name: Marketplace
- Hash: QmXdZDKnDX2o9qfupGDTXFM1xxspndHrHAGpbkWAPMs6Qk
- Block: 11111654
- Error: Failed to invoke handler 'handleBidCreated'
- Name: v39_8
- Hash: QmWex7boz79MGkYmcLbjDg4N13kLsLQAtTfLyjcz6RgJ9i
- Block: 11131520
- Error: Failed to invoke handler 'handleNewContributionProposal'
- Name: exchange
- Hash: QmWpFQJWVBkzTfabZL5DxnAvdhjP5FjbBW87jP2XcjyuUb
- Block: 11131875
- Error: Failed to invoke handler 'handleJoinPool'
- Name: Protocol Multy Raw
- Hash: QmS8ZBEgXisX7yEm8daSQmmVkwQ6wH6WU1B4nBkYKrjHo2
- Block: 11145982
- Error: Failed to invoke handler 'handleLendingPoolManagerUpdated'
- Name: KeeperDAO
- Hash: QmW6BrjSMPUSjMApTNYZShHi9XShgziC5YppGvqyjjAAX1
- Block: 11157922
- Error: Failed to invoke handler 'handleWithdrew'
koen84 commented 4 years ago

I'm going to link the existing issue #116 that also has P2 failing subgraphs commented.

fattox commented 4 years ago

Updated with 1 more i noticed that failed today, and 1 that @koen84 brought to my attention (verified on my own node).

koen84 commented 4 years ago

This one also crashed for me just now QmS8ZBEgXisX7yEm8daSQmmVkwQ6wH6WU1B4nBkYKrjHo2

fattox commented 4 years ago

Saw the same too, will add it to the list! šŸ‘

yasiryagi commented 4 years ago

Fresh today

101 11131875 QmWpFQJWVBkzTfabZL5DxnAvdhjP5FjbBW87jP2XcjyuUb Failed to process trigger in block #11131875 (68d3916d08e67b0bd7c502fd0ca2c8279871c2a72841390ff231d0e748a50444), transaction d956e1c73fb999c65e30a00c5e6cb3eceeb64cff835afb74d8fcaaab4750be2b: Failed to invoke handler 'handleJoinPool': Mapping aborted at ~lib/@graphprotocol/graph-ts/index.ts, line 772, column 4, with message: Value is not an i32. wasm backtrace: 0: 0x1ce7 - !<wasm function 87> 1: 0x256d - !<wasm function 135> 2: 0x2e0c - !<wasm function 167> -
100 11157922 QmW6BrjSMPUSjMApTNYZShHi9XShgziC5YppGvqyjjAAX1 Failed to process trigger in block #11157922 (135346b051565003d610f4a5d7b433c787d087829eaa1d1610921657b0d537d4), transaction e56b5fea884acb73377bd1f628042e560c47a730f3bf390d5d05b1c72b88f470: Failed to invoke handler 'handleWithdrew': Mapping aborted at generated/schema.ts, line 23, column 4, with message: Cannot save User entity without an ID wasm backtrace: 0: 0x10e8 - !<wasm function 41> 1: 0x189a - !<wasm function 90>
koen84 commented 4 years ago

I currently have these 5 that are not yet in the overview : Qmd8JSo29vQX3iP45JMVEL2zQJ6bQEMkqnWsoW3eRjMJEn 10612221 QmQrapV3GN6GnkMByUbf6Xrw1xVqSNAbQtNkXsy6xKAs15 10610090 QmW5UcMhXwXrMqRpTdT3MKB7HYDxbsp5oe9Atkuh4sgAA5 11079654 QmW6BrjSMPUSjMApTNYZShHi9XShgziC5YppGvqyjjAAX1 11039294 QmYPh4BHfJRszYBP7tnPFPHpKf2DdyHAtgRbE8PAnU1fZN 11085389

Would be good to get confirmation from others.

fattox commented 4 years ago

@yasiryagi QmWpFQJWVBkzTfabZL5DxnAvdhjP5FjbBW87jP2XcjyuUb - was already on the list. QmW6BrjSMPUSjMApTNYZShHi9XShgziC5YppGvqyjjAAX1 - can confirm it's broken for me (and @koen84 above). Will add to the list.

@koen84 Qmd8JSo29vQX3iP45JMVEL2zQJ6bQEMkqnWsoW3eRjMJEn - One of the few i'm not syncing, so can't confirm it myself. QmQrapV3GN6GnkMByUbf6Xrw1xVqSNAbQtNkXsy6xKAs15 - Working and fully indexed for me. QmW5UcMhXwXrMqRpTdT3MKB7HYDxbsp5oe9Atkuh4sgAA5 - Working and fully indexed for me. QmYPh4BHfJRszYBP7tnPFPHpKf2DdyHAtgRbE8PAnU1fZN - Working and fully indexed for me.

koen84 commented 4 years ago

QmWex7boz79MGkYmcLbjDg4N13kLsLQAtTfLyjcz6RgJ9i got "uncrashed" for me.

fattox commented 4 years ago

Still erroring out for me at block 11131520.

fattox commented 4 years ago

Just had these die on 1 node, but not the other. šŸ˜• QmUmgYJL3yp7EiSgxQ3zVxmDMJn3ZXDnYZWija4BWciEvu QmPSzSpAHozDWgqsa9FMKk2qd1xrhEZJfhGxskgz4b8HoQ

mindstyle85 commented 3 years ago

i am getting this on my subgraph QmbS7vmAWXJqsJEnAbvNSBYQXxCUmZWHFQygHPbyb3vy3N:

"fatalError": {
          "message": "Decoder error: Error(\"invalid type: null, expected a sequence\", line: 0, column: 0)"

full output:

{
  "data": {
    "indexingStatuses": [
      {
        "chains": [
          {
            "chainHeadBlock": {
              "number": "11177778"
            },
            "lastHealthyBlock": null,
            "latestBlock": {
              "number": "9568701"
            },
            "network": "mainnet"
          }
        ],
        "fatalError": {
          "message": "Decoder error: Error(\"invalid type: null, expected a sequence\", line: 0, column: 0)"
        },
        "health": "failed"
      }
    ]
  }
}
fattox commented 3 years ago

Are you sure that's not a ETH node issue? That one is still syncing for me.

mindstyle85 commented 3 years ago

@fattox yes pretty sure as all my other ones are syncing and no issues, and theres at least one other user with the same problem

I am guessing you somehow made it past the block where it breaks, but why it broke there i dont know, maybe something in the newer versions.. cant really say

trader-payne commented 3 years ago

I have it fully up to chain head as well.

mindstyle85 commented 3 years ago

if anyone wants to verify, just sync it from scratch again.. something is def broken.

yasiryagi commented 3 years ago

This just to confirm that I just hit

yasiryagi commented 3 years ago

QmW6BrjSMPUSjMApTNYZShHi9XShgziC5YppGvqyjjAAX1 Certainly broken

11157922 QmW6BrjSMPUSjMApTNYZShHi9XShgziC5YppGvqyjjAAX1 Failed to process trigger in block #11157922 (135346b051565003d610f4a5d7b433c787d087829eaa1d1610921657b0d537d4), transaction e56b5fea884acb73377bd1f628042e560c47a730f3bf390d5d05b1c72b88f470: Failed to invoke handler 'handleWithdrew': Mapping aborted at generated/schema.ts, line 23, column 4, with message: Cannot save User entity without an ID wasm backtrace: 0: 0x10e8 - !<wasm function 41> 1: 0x189a - !<wasm function 90>
yasiryagi commented 3 years ago

Saw the same too, will add it to the list!

Same here

11145982 QmS8ZBEgXisX7yEm8daSQmmVkwQ6wH6WU1B4nBkYKrjHo2 Failed to process trigger in block #11145982 (4e876c1c4cc2b7d3392a4f403e24f9c3683c31850dac7efa4853bf7a2d5dcd00), transaction 68b39527fda33dcc176bab32333a3e51612b13d6f033230831d8b65c709ab235: Failed to invoke handler 'handleLendingPoolManagerUpdated': Mapping aborted at raw/initializers.ts, line 271, column 4, with no message wasm backtrace: 0: 0x136b - !<wasm function 47> 1: 0x16fe - !<wasm function 59> 2: 0x17e1 - !<wasm function 63>
mindstyle85 commented 3 years ago

these to are dead too (still).....

Nov 27 00:28:23.293 WARN Trying again after trace_filter RPC call failed (attempt #10) with result Err(Decoder("Error(\"invalid type: null, expected a sequence\", line: 0, column: 0)")), subgraph_id: QmVviUCWpxxZuwekyHe87vspJsaugG1KDkfqEwjm3788ku, component: SubgraphInstanceManager > BlockStream Nov 27 00:28:23.701 INFO Scanning blocks [9736758, 9736758], range_size: 1, subgraph_id: QmP595e8r4VRPcKG5bfHUSN4ybbYnZkjgYkSHjfDw5YshY, component: SubgraphInstanceManager > BlockStream Nov 27 00:28:24.250 WARN Trying again after trace_filter RPC call failed (attempt #10) with result Err(Decoder("Error(\"invalid type: null, expected a sequence\", line: 0, column: 0)")), subgraph_id: QmP595e8r4VRPcKG5bfHUSN4ybbYnZkjgYkSHjfDw5YshY, component: SubgraphInstanceManager > BlockStream

is anyone event looking at these, theyre happening to multiple people, so its not like its just me.

yasiryagi commented 3 years ago

these to are dead too (still).....

Nov 27 00:28:23.293 WARN Trying again after trace_filter RPC call failed (attempt #10) with result Err(Decoder("Error("invalid type: null, expected a sequence", line: 0, column: 0)")), subgraph_id: QmVviUCWpxxZuwekyHe87vspJsaugG1KDkfqEwjm3788ku, component: SubgraphInstanceManager > BlockStream Nov 27 00:28:23.701 INFO Scanning blocks [9736758, 9736758], range_size: 1, subgraph_id: QmP595e8r4VRPcKG5bfHUSN4ybbYnZkjgYkSHjfDw5YshY, component: SubgraphInstanceManager > BlockStream Nov 27 00:28:24.250 WARN Trying again after trace_filter RPC call failed (attempt #10) with result Err(Decoder("Error("invalid type: null, expected a sequence", line: 0, column: 0)")), subgraph_id: QmP595e8r4VRPcKG5bfHUSN4ybbYnZkjgYkSHjfDw5YshY, component: SubgraphInstanceManager > BlockStream

is anyone event looking at these, theyre happening to multiple people, so its not like its just me.

Hi, both these are indexed for me, but during the indexing I have seen the error above which normally is ETH node connectivity or rate limiting.

trader-payne commented 3 years ago

These two look like trace errors. What eth archive node are you using? @yasiryagi

JB273 commented 3 years ago

Are you sure that's not a ETH node issue? That one is still syncing for me.

We are running this on an ETH Archive node (OpenEthereum 3.0.1) any options we should enable to make this work?

fattox commented 3 years ago

The two above are still in sync for me also. Using Open Eth 3.0.0 though.

JB273 commented 3 years ago

The two above are still in sync for me also. Using Open Eth 3.0.0 though.

What option have you on you ETH node enabled?

We have this now:

ExecStart=/home/node-admin/oe/openethereum \ --pruning=archive \ --no-warp \ --db-compaction=ssd \ --jsonrpc-hosts=all \ --jsonrpc-apis=all \ --min-peers=100 \ --max-peers=250 \ --cache-size-db=58000

fattox commented 3 years ago

You should have --tracing=on

fattox commented 3 years ago

Here's the non-networking side of my config:

[parity]
# Parity continously syncs the chain.
mode = "active"

[footprint]
# Increase performance on SSD.
db_compaction = "ssd"
# Compute and Store tracing data. (Enables trace_* APIs).
tracing = "on"
# Keep all state trie data. No pruning.
pruning = "archive"
# Enables Fat DB.
fat_db = "on"
# Database cache.
cache_size_db = 8192
# Blockchain cache.
cache_size_blocks = 2048
# Block import queue.
cache_size_queue = 2048
# State cache.
cache_size_state = 2048
trader-payne commented 3 years ago

You should have --tracing=on

Large oof mate @JB273