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

sync: failed to read block response stream #3286

Closed
EclesioMeloJunior opened this issue May 29, 2023 · 0 comments · Fixed by #3287
Closed

sync: failed to read block response stream #3286

EclesioMeloJunior opened this issue May 29, 2023 · 0 comments · Fixed by #3287

Comments

@EclesioMeloJunior
Copy link
Member

Describe the bug

  • Gossamer is failing to read the block response message from other peers, after executing the request (log line below)
2023-05-29T16:15:02Z DEBUG    [EXECUTING] worker 12D3KooWPVPzs42GvRBShdUMtFsk4SvnByrSdWqb6aeAAHvLMSLS: block request: BlockRequestMessage RequestedData=19 StartingBlock={6169473} Direction=0 Max=128	pkg=sync

it fails to read the full bytes

2023-05-29T16:15:03Z DEBUG    [FINISHED] worker 12D3KooWPVPzs42GvRBShdUMtFsk4SvnByrSdWqb6aeAAHvLMSLS: err: read stream error: failed to read entire message: expected 6517303 bytes, received 4177920 bytes	pkg=sync
@EclesioMeloJunior EclesioMeloJunior changed the title Failed to read block response stream sync: failed to read block response stream May 29, 2023
@EclesioMeloJunior EclesioMeloJunior mentioned this issue May 29, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(dot/network): remove maxReads limitation to read stream ChainSafe/gossamer
1 participant
@EclesioMeloJunior