After running yarn arcpatch D7197, I noticed that the commit before this one is D7155. Does this work depend on D7155? If so, can you specify the stack on Phabricator?
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Mar 27 2023
Nothing looks super surprising here, thanks!
lgtm!
nice this is very helpful
Fixes after in work in the subsequent diff
rebase before landing
When you're modifying SQLite database on native you should do two things:
- Update create_schema - this code is running on a fresh install/logout user (you did it properly)
- Add new migration which will update this table when existing users will update the app to a newer version. We were adding NOT EXISTS everywhere because of multiple crashes at that time, but I think it should work without this constraint (a lot of refactors were done to avoid problems). If you really want to make this code resistant you can use PRAGMA table_info() to check if the column exists and then execute ALTER TABLE.
Is this diff still in [draft] state? Or is it ready to review?
Is this diff still in [draft] state? Or is it ready to review?
address atuls comments
rebase before landing/updated order in stack so I can unblock landing this diff
Accepting to unblock but the pattern of copy-paste is concerning
Thanks for submitting!! I am clueless in Rust and this appears mostly Rust, so I will resign
Rebase to master
Set id to readonly
rebase before landing
rebase before landing
Rebase
Rebase
Rebase before landing
Rebase before landing
Rebase before landing
Rebase before landing
Clarify that it's in the timezone of the keyserver
Requesting changes for inline comment, and for the discussion previously in D7076
Rebase before landing
Rebase before landing
Rebase before landing