Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug] substreams powered subgraph is healthy even if its failed #5749

Open
1 of 3 tasks
shiyasmohd opened this issue Dec 30, 2024 · 0 comments · May be fixed by #5750
Open
1 of 3 tasks

[Bug] substreams powered subgraph is healthy even if its failed #5749

shiyasmohd opened this issue Dec 30, 2024 · 0 comments · May be fixed by #5750
Assignees
@shiyasmohd
Labels
area/substreams Substreams related issues bug Something isn't working

Comments

@shiyasmohd
Copy link
Contributor

shiyasmohd commented Dec 30, 2024 •
edited
Loading

Bug report

SPS is shown as healthy and has no errors returned in index-node api even if subgraph is failed with an error.
When checking logs, it has failed with the below error

ERRO Subgraph instance failed to run: error while executing at wasm backtrace:\n    0: 0x43f2 - <unknown>!src/mappings/handleTriggers: Entity Token[0x4200000000000000000000000000000000000006]: missing value for non-nullable field `totalSupply`: Entity Token[0x4200000000000000000000000000000000000006]: missing value for non-nullable field `totalSupply`: error while executing at wasm backtrace:\n    0: 0x43f2 - <unknown>!src/mappings/handleTriggers: Entity Token[0x4200000000000000000000000000000000000006]: missing value for non-nullable field `totalSupply`: Entity Token[0x4200000000000000000000000000000000000006]: missing value for non-nullable field `totalSupply`, sgd: XXXXX, subgraph_id: Qmc8XkaebEhdtMiTqWsTA9JzM1xvFsd7HjonFXKBU5bXSk,

Index-node API response

{
    "data": {
        "indexingStatuses": [
            {
                "subgraph": "Qmc8XkaebEhdtMiTqWsTA9JzM1xvFsd7HjonFXKBU5bXSk",
                "synced": false,
                "health": "healthy",
                "fatalError": null,
                "nonFatalErrors": []
            }
        ]
    }
}

Relevant log output

ERRO Subgraph instance failed to run: error while executing at wasm backtrace:\n    0: 0x43f2 - <unknown>!src/mappings/handleTriggers: Entity Token[0x4200000000000000000000000000000000000006]: missing value for non-nullable field `totalSupply`: Entity Token[0x4200000000000000000000000000000000000006]: missing value for non-nullable field `totalSupply`: error while executing at wasm backtrace:\n    0: 0x43f2 - <unknown>!src/mappings/handleTriggers: Entity Token[0x4200000000000000000000000000000000000006]: missing value for non-nullable field `totalSupply`: Entity Token[0x4200000000000000000000000000000000000006]: missing value for non-nullable field `totalSupply`, sgd: XXXXX, subgraph_id: Qmc8XkaebEhdtMiTqWsTA9JzM1xvFsd7HjonFXKBU5bXSk,

IPFS hash

Qmc8XkaebEhdtMiTqWsTA9JzM1xvFsd7HjonFXKBU5bXSk

Subgraph name or link to explorer

No response

Some information to help us out

  • Tick this box if this bug is caused by a regression found in the latest release.
  • Tick this box if this bug is specific to the hosted service.
  • I have searched the issue tracker to make sure this issue is not a duplicate.

OS information

None
@shiyasmohd shiyasmohd added bug Something isn't working area/substreams Substreams related issues labels Dec 30, 2024
@shiyasmohd shiyasmohd self-assigned this Dec 30, 2024
@shiyasmohd shiyasmohd linked a pull request Dec 30, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shiyasmohd shiyasmohd

Labels
area/substreams Substreams related issues bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

improve error handling of substreams powered subgraphs graphprotocol/graph-node
2 participants
@shiyasmohd and others