[Bug] Cannot get info of chain
Bug report
graphman chain info <name> does not seem to work and complains of a missing parent hash. I'm running v0.32.0.
Relevant log output
root@goldskyraw-indexer-0-graph-node-5dd9464b5b-26n7g:/# graphman chain info mainnet
Error: missing field `parentHash`
root@goldskyraw-indexer-0-graph-node-5dd9464b5b-26n7g:/# graphman chain info matic
Error: missing field `parentHash`
IPFS hash
No response
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.
- [X] I have searched the issue tracker to make sure this issue is not a duplicate.
OS information
None
Hey @paymog , is there any additional steps for reproducing this? Im not able to reproduce this.
Unfortunately I don’t know how to reproduce either 😕
Defenetly wierd, but i wonder whats happening. This was working before 0.32 right?
Defenetly wierd, but i wonder whats happening. This was working before 0.32 right?
I never tried this in an older version so I'm not sure 🙁
@paymog are you using a Firehose or an RPC for the block ingestor?
@paymog are you using a Firehose or an RPC for the block ingestor?
I'm using firehose for the two chains in the original example
This bug can be reproduced on a chain synching entirely using Firehose.
graphman chain info matic
Error: missing field `parentHash`
graphman chain info mainnet
Error: missing field `parentHash`
It must be related to how the blocks are stored when using firehose ingestor: the graphman assumes there will be data that is inexistent.
thanks @sduchesneau - @incrypto32 do you know if we store the parentHash with a Firehose block ingestor, or might that be the source of the issue?
Looks like this issue has been open for 6 months with no activity. Is it still relevant? If not, please remember to close it.