Foundry376/Mailspring
1
1
Fork 0
mirror of https://github.com/Foundry376/Mailspring.git synced 2024-11-11 01:54:40 +08:00
Code Issues Projects Releases Packages Wiki Activity

Sentry fix: reproduce issue with reminder metadata not transfered to thread, increase timeout

Browse source
This commit is contained in:
Ben Gotow 2019-06-22 23:47:04 -05:00
parent 808c7581a4
commit 1c485ae213
1 changed files with 11 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
app/internal_packages/send-reminders/lib/send-reminders-utils.ts
View file

@ -90,14 +90,18 @@ export async function findMessage({ accountId, headerMessageId }) {
export async function transferReminderMetadataFromDraftToThread({ accountId, headerMessageId }) {
let message = await findMessage({ accountId, headerMessageId });
if (!message) {
// The task has just completed, wait a moment to see if the message appears. Testing to
// see whether this resolves https://sentry.io/foundry-376-llc/mailspring/issues/363208698/
await Promise.delay(1500);
let delay = [1500, 1500, 10000, 10000];
// The sent message should already be synced, but if the send taks was interrupted and completed
// without finalizing / cleaning up, we may need to go through a sync cycle. Do this before giving up.
let ms = 0;
while (!message && (ms = delay.shift())) {
await Promise.delay(ms);
message = await findMessage({ accountId, headerMessageId });
if (!message) {
throw new Error('SendReminders: Could not find message to update');
}
}
if (!message) {
throw new Error('SendReminders: Could not find message to update');
}
const metadata = message.metadataForPluginId(PLUGIN_ID) || {};