Query to Sigs: returns record with the only last msgHash in tx logs

[davaymne]

WHAT: Query to Sigs: returns record with the only last msgHash in tx logs.

It could be a case where there are multiple SignMsg logs in the same tx https://etherscan.io/tx/0x1e206ce100e2c9c85dbf6365798e2e6ccbf4e30d9499a00699e86531c6426778#eventlog

Query:

{
  sigs (where: {id: "0x1e206ce100e2c9c85dbf6365798e2e6ccbf4e30d9499a00699e86531c6426778"}){
    id
    account
    timestamp
    msgHash
  }
}

Output:

{
  "data": {
    "sigs": [
      {
        "id": "0x1e206ce100e2c9c85dbf6365798e2e6ccbf4e30d9499a00699e86531c6426778",
        "account": "0xcb7ec73fd2bca2596794804a6ef5475d0dc4f427",
        "timestamp": "1655486898",
        "msgHash": "0x051294081b7decc21d5bfb0eb4b088564850e9129126ec29477dfe0551ffde91"
      }
    ]
  }
}

Returns only last log rather the list of SignMsg logs.

[ChaituVR]

We are not using sigs anymore because of this. you have some use case?

[davaymne]

So far, we use your subgraph as an excellent example for practicing subgraph migration from The Graph protocol to Subsquid protocol (which is currently running Testnet) and bumped into this data discrepancy.