chore: use the latest substreams version#18
chore: use the latest substreams version#18ppoliani wants to merge 1 commit intostreamingfast:mainfrom
Conversation
| firehose-real-time-tolerance: 999999999s | ||
| relayer-max-source-latency: 999999999s | ||
|
|
||
| common-live-blocks-addr: "" |
There was a problem hiding this comment.
@maoueh if I don't set this to empty string then when I run
grpcurl -plaintext -import-path ../proto -import-path ./proto -proto sf/aptos/type/v1/type.proto -proto sf/firehose/v2/firehose.proto -d '{"start_block_num": 0}' localhost:18015 sf.firehose.v2.Stream.BlocksI get the following error:
Failed to dial target host "localhost:18015": dial tcp [::1]:18015: connect: connection refused
This was not the case before I updated the substreams version.
I did debug it a and realized that this value is set the flow get stuck at select https://github.com/streamingfast/firehose/blob/develop/app/firehose/app.go#L183 and doesn't reach the launch line https://github.com/streamingfast/firehose/blob/develop/app/firehose/app.go#L193.
Is there a reason why this happens with the latest substreams version?
There was a problem hiding this comment.
This code in firehose component that wait for the hub to be "live" exist since a long time, definitely not coming from an upgrade of the dependency alone.
But I think the way we detect it changed indeed. Now you need to have one-blocks files that "links" with live blocks coming from the live source which means syncing a testnet will be ready only once blocks are live.
Since this is syncing devnet, I imagine it will indeed not work anymore.
There was a problem hiding this comment.
ow you need to have one-blocks files that "links" with live blocks coming from the live source which means syncing a testnet will be ready only once blocks are live.
Pardon my ignorance, but I'm not sure I fully understand this concepts 😆
one-blocks are the files stored locally, right? From what I've notices, this is files are created when the console reader gets the logs from the stdout and decodes the block data which are then stored. So what does this sentence mean?
syncing a testnet will be ready only once blocks are live.
Doe sit mean that the endpoint on port :18015 will be available once the full network is synced?
maoueh
left a comment
maoueh
left a comment
There was a problem hiding this comment.
Do you want me to merge that now?
| firehose-real-time-tolerance: 999999999s | ||
| relayer-max-source-latency: 999999999s | ||
|
|
||
| common-live-blocks-addr: "" |
There was a problem hiding this comment.
This code in firehose component that wait for the hub to be "live" exist since a long time, definitely not coming from an upgrade of the dependency alone.
But I think the way we detect it changed indeed. Now you need to have one-blocks files that "links" with live blocks coming from the live source which means syncing a testnet will be ready only once blocks are live.
Since this is syncing devnet, I imagine it will indeed not work anymore.
2 participants
No description provided.