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

Feature/2595 l1 sync deadlock #2616

Merged
merged 6 commits into from
Oct 5, 2023
Merged

Conversation

joanestebanr
Copy link
Contributor

Closes #2595

What does this PR do?

  • It keep running producer instead of stopping to do the reset
  • Fix some errors due this change of behaviour

Reviewers

Main reviewers:
@ARR552

@joanestebanr joanestebanr requested a review from ARR552 as a code owner October 4, 2023 19:47
@cla-bot cla-bot bot added the cla-signed label Oct 4, 2023
synchronizer/l1_syncstatus.go Show resolved Hide resolved
synchronizer/l1_workers.go Show resolved Hide resolved
@joanestebanr joanestebanr self-assigned this Oct 5, 2023
@joanestebanr joanestebanr merged commit bf82f69 into develop Oct 5, 2023
@joanestebanr joanestebanr deleted the feature/2595-l1_sync-deadlock branch October 5, 2023 08:30
@joanestebanr joanestebanr added this to the v0.4.0 milestone Oct 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Synchronizer L1 parallel: get stuck after a new ForkId
2 participants