fix: 9142 search results disappearing#11032
Open
numericOverflow wants to merge 2 commits into
Open
Conversation
Contributor
|
✅ Validation Passed: All report and feature-flag labels are correctly set. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
When a remote search saves an envelope-only message and a subsequent sync replaces it with the full message, the
database.replace()call deletes and re-inserts the row. This orphans the correspondingthreadsentry (foreign key onmessages.id), causing the message to disappear from search results.Switching from
replace()toupdate()preserves the row ID and keeps the thread reference intact.Issue
Fixes #9142
Test plan
SaveMessageOperationsTest)AI disclosure
AI was used to assist in tracking down source of bug, correcting & drafting this pull request description. It wasn't a simple vibe code job, I did interrogate it on plan and helped it choose the most appropriate, reliable and logical solution.
I tested the resulting build on my android device and confirmed it fixed the bug that has been outstanding for several years.
Supporting information:
Report from Claude 4.6 (High)
root-cause-analysis.md
Solution that was implemented after discussion and design choices from Claude 4.6 (High)
final-solution-proposal.md
report: include