issue: ENG-9632
If we fail to fetch usres device list for a whole day, we can assume that this is not due to identity temporary data inconsistency. And if a user is a member of a DM, and their device list is not present on the identity, then we know for certain that they deleted their account.
There is only one catch here - if the request times out we shouldn't be deleting the user. Created ENG-9725 to address this
Details
Details
Tested that a user whose device list failed to be fetched for a long time gets deleted and they get removed from threads, users store and aux user store.
Checked that a user whose lastChecked was updated does not get removed from threads and other stores
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Branch
- inka/missing_peers
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
lib/shared/dm-ops/dm-op-utils.js | ||
---|---|---|
178–202 | It might be a good idea to make the dependency between nonDeletedUsers and deletedUsers explicit by creating a function. |