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

RPC deadline should not fail sync, rather next sync peer should be selected #4648

Closed
sdbondi opened this issue Sep 8, 2022 · 0 comments · Fixed by #4649
Closed

RPC deadline should not fail sync, rather next sync peer should be selected #4648

sdbondi opened this issue Sep 8, 2022 · 0 comments · Fixed by #4649
Assignees
@sdbondi

Comments

@sdbondi
Copy link
Member

sdbondi commented Sep 8, 2022

No description provided.

@sdbondi sdbondi self-assigned this Sep 8, 2022
@sdbondi sdbondi mentioned this issue Sep 8, 2022
Merged
stringhandler pushed a commit that referenced this issue Sep 9, 2022
@sdbondi
fix(core/sync): handle deadline timeouts by changing peer (#4649)
5ed997c 
Description
---
If the RPC deadline is reached, immediately move on to the next sync peer.

Motivation and Context
---
Fixes #4648

How Has This Been Tested?
---
Manually, header, pruned and block sync
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sdbondi sdbondi

Labels
None yet
Projects
Tari Esme Testnet
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(core/sync): handle deadline timeouts by changing peer sdbondi/tari
1 participant
@sdbondi