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.

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

[Audit] - Fetch Blocks Properly when Leader Consecutively #3462

Closed
bfish713 opened this issue Jul 18, 2024 · 0 comments · Fixed by #3491
Closed

[Audit] - Fetch Blocks Properly when Leader Consecutively #3462

bfish713 opened this issue Jul 18, 2024 · 0 comments · Fixed by #3491

Comments

@bfish713
Copy link
Collaborator

What is this task and why do we need to work on it?

The transactions task has logic to detect missed views and fetch a block for the next view or the current view. However we could be the leader for both the current view and the next view, in that case we'll only get a block for the first view we lead

What work will need to be done to complete this task?

No response

Are there any other details to include?

No response

What are the acceptance criteria to close this issue?

Fix the issue and write a test where a node leads twice after a skipped view.

Branch work will be merged to (if not the default branch)

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants