-
Notifications
You must be signed in to change notification settings - Fork 269
fix(messenger): defer mailserver history sync when app is in background #7508
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
Closed
Closed
Changes from 1 commit
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
d793ad5
fix(messenger): defer mailserver history sync when app is in background
xAlisher 9aac52a
fix(filter): suppress Waku filter-subscription renewal in background
xAlisher ee0cd6c
chore(deps): remove orphaned go-waku checksum after replace directive
xAlisher 72956f2
chore(deps): bump go-waku fork to 9f836193 (health-check ping suppres…
xAlisher 26b2e81
refactor(messenger): fold background-mode into ToBackground/ToForeground
xAlisher 5ab25f5
refactor(node): register Messenger as a Pausable service
xAlisher File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -159,7 +159,11 @@ func (m *Messenger) checkForStorenodeCycleSignals() { | |
| if ok { | ||
| signal.SendStoreNodeAvailable(&ms) | ||
| } | ||
| m.asyncRequestAllHistoricMessages() | ||
| // Skip history sync when backgrounded; SetAppBackground(false) | ||
| // will trigger it when the app returns to foreground. | ||
| if !m.backgroundMode.Load() { | ||
|
Comment on lines
+162
to
+164
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Instead of skipping store node requests, why don't we just completely disconnect from storenodes and stop the |
||
| m.asyncRequestAllHistoricMessages() | ||
| } | ||
| } | ||
| } | ||
| } | ||
|
|
||
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@xAlisher just a few lines above we already have ToForeground()/ToBackground() functions.
ToForegroundalready calls asyncRequestAllHistoricMessages() and as I see you're now adding a second, parallel lifecycle pair (via SetAppBackground). Why not reuse?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also we should think if
shouldSync()should be called when doingm.asyncRequestAllHistoricMessages()inToForeground().