-
Notifications
You must be signed in to change notification settings - Fork 175
Fix hang in nested fixpoint iteration #871
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
base: master
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for salsa-rs canceled.
|
CodSpeed Performance ReportMerging #871 will degrade performances by 5.34%Comparing Summary
Benchmarks breakdown
|
4140252
to
a6d9b6c
Compare
tracing::debug!( | ||
"Waiting for {head_index:?} results in a cycle, return {database_key_index:?} once all other cycle heads completed to allow the outer cycle to make progress." | ||
); | ||
hit_cycle = true; |
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.
I changed this to early-return in #861 but I think that was incorrect. Not early-returning fixes the ty panic for kopf
. I might spend some more time to come up with a test case for it but I might also just leave it at it (I already spent an entire week on this :s)
This does not fix all occurences of the cycle iteration panic, I can still reproduce it on pandas-stubs |
This fixes a hang in multithreaded fixpoint iteration where the
Memo::provisional_retry
retried over and over again because all its cycle heads other than itself were finalized at this point.This also fixes the panic from the
kopf
repro listed in #831