Fix deadlock caused by ListDatabaseObserver.startObserving() changes #2252
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.
🔗 Issue Links
None
🎯 Goal
This PR reverts this change: #2177 which caused a deadlock in
@CoreDataLazy
because of the usage of@Atomic
. Besides this, that change also makes the Channel List Loading less performant because the LazyCachedCollection is not really being used, and it is not lazy with that change.With the newly introduced
logout()
the fix above is not needed anymore, since we can guarantee there won't be nullable items.☑️ Contributor Checklist