Closed azf20 closed 2 years ago
The issue was not in client side, but in the firehose.
fixed here: https://github.com/streamingfast/bstream/commit/268abefde7b452b728172a8cc7ac46ec7098a835 deployed to our current prod endpoint with this flag:
--common-first-streamable-block=9820214 (prod) --common-first-streamable-block=42376923 (testnet)
tested like this:
grpcurl -H "Authorization: Bearer $SF_TOKEN" -d "{\"start_block_num\":1234}" mainnet.near.streamingfast.io:443 dfuse.bstream.v1.BlockStreamV2/Blocks
Let me know if this resolves the issue and if it can be closed.
Thanks @sduchesneau ! I deployed a near-mainnet
subgraph with startBlock: 0
and indexing started smoothly, closing this issue
If the provided startBlock is earlier than the Firehose's first block, the subgraph does not start indexing and hangs