You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use chain-sync at the beginning to get the available block range and then leave it in the Idle state, which has a (random) timeout. This causes the connection to get randomly closed after the timeout expires if we're still in the middle of receiving blocks via block-fetch.
This probably requires blinklabs-io/gouroboros#597 to fix properly so that we can re-use chain-sync later on the same connection.
The text was updated successfully, but these errors were encountered:
We use chain-sync at the beginning to get the available block range and then leave it in the Idle state, which has a (random) timeout. This causes the connection to get randomly closed after the timeout expires if we're still in the middle of receiving blocks via block-fetch.
This probably requires blinklabs-io/gouroboros#597 to fix properly so that we can re-use chain-sync later on the same connection.
The text was updated successfully, but these errors were encountered: