-
Notifications
You must be signed in to change notification settings - Fork 107
fix(concurrency): stop the transaction committer when the scheduler is done #1989
Conversation
ac1f6de
to
a1b8d05
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @barak-b-starkware and @noaov1)
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1989 +/- ##
=======================================
Coverage 78.61% 78.61%
=======================================
Files 62 62
Lines 8895 8895
Branches 8895 8895
=======================================
Hits 6993 6993
Misses 1455 1455
Partials 447 447 ☔ View full report in Codecov by Sentry. |
@barak-b-starkware said his flow test got stuck in an infinite loop, so I tried to think of places where the scheduler might get stuck. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then @OriStarkware must see this bug in his env. Please make sure
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @barak-b-starkware, @meship-starkware, @noaov1, and @OriStarkware)
Why do we need this assertion? It feels trivial/redundant. What do I miss here? Code quote: assert!(
*self.commit_index_guard < self.scheduler.chunk_size,
"The commit index must be less than the chunk size, since the scheduler is not done."
); |
This change is