Fix missing anti-revoke deleted DB migration / chat lag#1
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
This PR fixes WhatsApp conversation lag caused by repeated WAE deleted-message database 5 -> 11 migration failures.
Fixed
delmessages.dbschema version 5 to 6, allowing existing WAE deleted-message history databases to migrate forward to the current schema.Notes
Device was running an older version of WAE which used DB version 5.
LSPosed modules logs showed
ConversationItemListenerrepeatedly catching and logging:Log produced on
AntiRevoke.bindRevokedMessageUI()when WhatsApp renders conversation rows. Causing lag even with default WAE settings.Validation
GH Releases: https://github.com/JSJ-Experiments/WaEnhancer/releases/tag/debug-2ebe945
GH Actions run: https://github.com/JSJ-Experiments/WaEnhancer/actions/runs/25955403989