You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please open an issue with this stack trace at https://github.com/nodejs/node/issues at assert (internal/assert.js:14:11) at JSStreamSocket.doWrite (internal/js_stream_socket.js:165:5) at JSStream.onwrite (internal/js_stream_socket.js:33:57) at Socket.ondata (internal/js_stream_socket.js:77:22) at Socket.emit (events.js:314:20) at addChunk (_stream_readable.js:297:12) at readableAddChunk (_stream_readable.js:272:9) at Socket.Readable.push (_stream_readable.js:213:10) at TCP.onStreamRead (internal/stream_base_commons.js:188:23)
Platform
Linux, Synology DS215
node red v3.0.2
Subsystem
No response
What steps will reproduce the bug?
does appera randomly within weeks
specific node cannot be identified
How often does it reproduce? Is there a required condition?
does appera randomly within weeks
What is the expected behavior? Why is that the expected behavior?