Juan Tejada 964bc3208f [local-sync] syncback(Part 4): Don't always mark INPROGRESS tasks as failed at beginning of sync ... Summary: Previously, if you were to close the app while you had any tasks queued, these would be marked as failed the next time you open the app, showing an annoying error message and reverting any optimisitic actions. However, we don't need to be so defensive about retrying tasks because the only tasks we can't retry are the Sending tasks. All of the other tasks like moving or changing labels are fine to retry (trying move the same set of uids twice wont cause an error) This commit adds an extra status to syncback requests, "NOTRETRYABLE". Only NOTRETRYABLE requests will be marked as failed at the beginning of the sync loop, and any INPROGRESS tasks will be marked as NEW so they can be retried Depends on D3896 Test Plan: manual Reviewers: mark, evan, spang, halla Reviewed By: evan, halla Differential Revision: https://phab.nylas.com/D3898		2017-02-13 13:48:29 -08:00
..
isomorphic-core	[iso-core] Detect more offline errors when sending	2017-02-13 12:18:45 -08:00
local-private	[local-sync] Don't crash app when reporting error and id not available	2017-02-09 09:27:36 -08:00
local-sync	[local-sync] syncback(Part 4): Don't always mark INPROGRESS tasks as failed at beginning of sync	2017-02-13 13:48:29 -08:00