-
Notifications
You must be signed in to change notification settings - Fork 13.1k
fix: Add loading state recovery over RoomHistoryManager.getMore
#36006
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Looks like this PR is ready to merge! 🎉 |
🦋 Changeset detectedLatest commit: 477264d The changes in this PR will be included in the next version bump. This PR includes changesets to release 36 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #36006 +/- ##
===========================================
- Coverage 64.80% 64.70% -0.10%
===========================================
Files 3099 3248 +149
Lines 92157 95319 +3162
Branches 17667 17899 +232
===========================================
+ Hits 59718 61677 +1959
- Misses 29674 30736 +1062
- Partials 2765 2906 +141
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
https://rocketchat.atlassian.net/browse/ARCH-1609
Proposed changes (including videos or screenshots)
It handles rejections inside the
RoomHistoryManager.getMoremethod (that usually occur during user logout) to not lock the room in a permanent loading state.Issue(s)
Steps to test or reproduce
Further comments
It's specially connected with flakyness of E2E encryption tests.