fix_: use 24h batches to retrieve message history #16813
+1
−1
Conversation
This file contains 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
richard-ramos
requested review from
iurimatias
and removed request for
a team
Jenkins Builds
|
|
Just to get back on this. I tested that the other day. I noticed some issue with messages are not showing up without force fetching them. Talked to @richard-ramos and @jrainville and it feels like Jo saw similar problem some time ago. We dont yet know how to mitigate this. Other than that, history was delivered fine |
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.
Instead of retrieving 30d of messages, split the request in 24h batches.
Requires: status-im/status-go#6115
To test this:
Ensure that profiles restore from backup successfully, as well as curated communities, and message history older than 24h