-
Notifications
You must be signed in to change notification settings - Fork 54
UnhandledPromiseRejectionWarning: Handle missing To field #9
Comments
This comment has been minimized.
This comment has been minimized.
I was able to preproduce the problem. Can you please share your pm2 config? |
I'll update, thanks.
pm2 vanilla, i didn't touch anything after install it. The file
module_conf.json totally empty (`{}`). Im not sure of wich conf do you talk.
I launch it vía script with pm2 command `pm2 --name email start npm --
start --watch`
~~ Self signed ~~
El jue., 27 jun. 2019 a las 6:32, Aravindo Wingeier (<
notifications@github.com>) escribió:
… I pushed an update, please try again.
Can you please share your pm2 config?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#9?email_source=notifications&email_token=AB4TAARZ2J2Z3QLNTGGYAZDP4Q7E3A5CNFSM4H3XBEHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYVUPTY#issuecomment-506152911>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB4TAASJOYZKKXP6XLXMYFDP4Q7E3ANCNFSM4H3XBEHA>
.
|
Maybe you could add to https://github.com/synox/void-mail/blob/master/docs/installation.md how to use pm2. I am working on a patch, its coming soon today. |
Commit e818f06 should resolve the issue. Please test. |
To clarify:
Shoud I update right now or wait for the patch you said now?
~~ Self signed ~~
El jue., 27 jun. 2019 a las 7:43, Aravindo Wingeier (<
notifications@github.com>) escribió:
… Maybe you could add to
https://github.com/synox/void-mail/blob/master/docs/installation.md how
to use pm2.
I am working on a patch, its coming soon today.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#9?email_source=notifications&email_token=AB4TAASIBINJKSWRIGGMDE3P4RHOXA5CNFSM4H3XBEHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYV7ZYA#issuecomment-506199264>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB4TAAX3H6SMPW47SMU6VKLP4RHOXANCNFSM4H3XBEHA>
.
|
You can update now. |
Fixed, thanks. |
The problem is there again. Seems that is being triggered by a new email. 0|email | > void-mail@0.0.0 start /root/email /root/.pm2/logs/email-error.log last 15 lines: |
System keeps working, but there's no report about the number of emails on system or other.
[TAILING] Tailing last 15 lines for [0] process (change the value with --lines option)
/root/.pm2/logs/email-out.log last 15 lines:
0|email |
0|email | > void-mail@0.0.0 start /root/email
0|email | > node ./bin/www
0|email |
/root/.pm2/logs/email-error.log last 15 lines:
0|email | (node:1969) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'flatMap' of undefined
0|email | at ImapService._createMailSummary (/root/email/mailbox/imap-service.js:166:5)
0|email | at mails.forEach.mail (/root/email/mailbox/imap-service.js:223:11)
0|email | at Array.forEach ()
0|email | at ImapService._getMailHeadersAndPublish (/root/email/mailbox/imap-service.js:219:10)
0|email | at process._tickCallback (internal/process/next_tick.js:68:7)
0|email | (node:1969) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
0|email | (node:1969) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
The text was updated successfully, but these errors were encountered: