mirror of
https://github.com/Foundry376/Mailspring.git
synced 2024-09-24 09:16:07 +08:00
5810bb6b79
Summary: See https://github.com/mscdex/node-imap/issues/585 for details. This issue was causing us constantly run the sync loop without pauses, i.e. every next sync loop was scheduled immediately. Currently, when we receive a new `'mail'`event, we trigger a new sync loop. Previously, when this happened while a sync loop was already in progress we would just ignore the event. However, my recent patch keeps track of how many times we tried to start a sync loop while one was already in progress. If the number of times this happens is > 0, it will schedule the next sync loop immediately (as opposed to waiting a constant amount seconds before the next loop). The problem is that this new logic is making the sync worker always schedule the next sync loop immediately (without pausing for a few seconds). This is due to the following chain of events (assume we are just syncing `all` and `trash` folders): This commit is a temporary workaround to this problem. Test Plan: manual Reviewers: evan Reviewed By: evan Differential Revision: https://phab.nylas.com/D3537 |
||
|---|---|---|
| .. | ||
| local-api | ||
| local-sync-dashboard | ||
| local-sync-worker | ||
| models | ||
| new-message-processor | ||
| shared | ||