LiquidThreads's onArticleMoveComplete only does 500 threads immediately (the rest go to the job queue). To work around this (and the fact that LQT has commit()'s nowhere except migrateDatabase, which I think is causing the lag issue that's breaking conversions here), we can call synchroniseArticleData ourselves with no limit.
Description
Description
Related Objects
Related Objects
Event Timeline
Comment Actions
Change 202979 had a related patch set uploaded (by Mattflaschen):
WIP: LQT maintenance refactoring
Comment Actions
Apparently this is invalid. @aaron pointed out that LQT was using $dbw->update() with a LIMIT, but the LIMIT was being totally ignored since it's not supported by update().