node-red / node-red/node-red-nodes
Email In Node Crashed Node-RED
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 612
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 3
Description
10 Dec 09:50:09 - [info] [e-mail in:a] Checking IMAP for new messages
10 Dec 09:50:09 - [red] Uncaught Exception:
10 Dec 09:50:09 - TypeError: Cannot read property 'type' of undefined
at Connection._resUntagged (C:\Users\julia\AppData\Roaming\nvm\v6.9.1\node_modules\node-red\node_modules\imap\lib\Connection.js:
1260:51)
at Parser.<anonymous> (C:\Users\julia\AppData\Roaming\nvm\v6.9.1\node_modules\node-red\node_modules\imap\lib\Connection.js:190:1
0)
at emitOne (events.js:96:13)
at Parser.emit (events.js:188:7)
at Parser._resUntagged (C:\Users\julia\AppData\Roaming\nvm\v6.9.1\node_modules\node-red\node_modules\imap\lib\Parser.js:271:10)
at Parser._parse (C:\Users\julia\AppData\Roaming\nvm\v6.9.1\node_modules\node-red\node_modules\imap\lib\Parser.js:137:16)
at Parser._tryread (C:\Users\julia\AppData\Roaming\nvm\v6.9.1\node_modules\node-red\node_modules\imap\lib\Parser.js:82:15)
at TLSSocket.Parser._cbReadable (C:\Users\julia\AppData\Roaming\nvm\v6.9.1\node_modules\node-red\node_modules\imap\lib\Parser.js
:53:12)
at emitNone (events.js:86:13)
at TLSSocket.emit (events.js:185:7)
at emitReadable_ (_stream_readable.js:432:10)
at emitReadable (_stream_readable.js:426:7)
at readableAddChunk (_stream_readable.js:187:13)
at TLSSocket.Readable.push (_stream_readable.js:134:10)
at TLSWrap.onread (net.js:548:20)
at Socket.ondata (_stream_wrap.js:58:20)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)
at readableAddChunk (_stream_readable.js:176:18)
at Socket.Readable.push (_stream_readable.js:134:10)
at TCP.onread (net.js:548:20)
Running on Windows 10 (Windows_NT 10.0.14393 x64 LE), Node.js v6.9.1, latest Node-RED v0.15.2
Restarting causes another error:
10 Dec 14:03:02 - [info] [e-mail in:a] Checking IMAP for new messages
10 Dec 14:03:03 - [red] Uncaught Exception:
10 Dec 14:03:03 - TypeError: Cannot set property 'name' of undefined
at Connection.<anonymous> (C:\Users\julia\AppData\Roaming\nvm\v6.9.1\node_modules\node-red\node_modules\imap\lib\Connection.js:4
26:22)
at Connection._resTagged (C:\Users\julia\AppData\Roaming\nvm\v6.9.1\node_modules\node-red\node_modules\imap\lib\Connection.js:15
30:22)
at Parser.<anonymous> (C:\Users\julia\AppData\Roaming\nvm\v6.9.1\node_modules\node-red\node_modules\imap\lib\Connection.js:193:1
0)
at emitOne (events.js:96:13)
at Parser.emit (events.js:188:7)
at Parser._resTagged (C:\Users\julia\AppData\Roaming\nvm\v6.9.1\node_modules\node-red\node_modules\imap\lib\Parser.js:175:10)
at Parser._parse (C:\Users\julia\AppData\Roaming\nvm\v6.9.1\node_modules\node-red\node_modules\imap\lib\Parser.js:139:16)
at Parser._tryread (C:\Users\julia\AppData\Roaming\nvm\v6.9.1\node_modules\node-red\node_modules\imap\lib\Parser.js:82:15)
at TLSSocket.Parser._cbReadable (C:\Users\julia\AppData\Roaming\nvm\v6.9.1\node_modules\node-red\node_modules\imap\lib\Parser.js
:53:12)
at emitNone (events.js:86:13)
at TLSSocket.emit (events.js:185:7)
at emitReadable_ (_stream_readable.js:432:10)
at emitReadable (_stream_readable.js:426:7)
at readableAddChunk (_stream_readable.js:187:13)
at TLSSocket.Readable.push (_stream_readable.js:134:10)
at TLSWrap.onread (net.js:548:20)
at Socket.ondata (_stream_wrap.js:58:20)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)
Node-RED is now unstartable. I'll have to revert to the backup flow file.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the e-mail in node and reproduce the IMAP failure using the reported Windows and Node.js versions. Trace the errors through node_modules/imap/lib/Connection.js and Parser.js, especially the reported _resUntagged and _resTagged locations. Done means the e-mail check no longer crashes Node-RED or leaves it unable to start.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100