Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

On message receive - Uncaught Exception: TypeError: Cannot assign to read only property 'writeQueueSize' of object '#<TCP>' #23

Open
potatoronin opened this issue Feb 12, 2021 · 2 comments
Open

On message receive - Uncaught Exception: TypeError: Cannot assign to read only property 'writeQueueSize' of object '#<TCP>' #23

potatoronin opened this issue Feb 12, 2021 · 2 comments
Labels
V3 Marked issue will be fixed (resolved) in version 3

Comments

@potatoronin
Copy link 

TypeError: Cannot assign to read only property 'writeQueueSize' of object '#<TCP>'
    at _clone (/usr/lib/node_modules/node-red/node_modules/clone/clone.js:162:16)
    at _clone (/usr/lib/node_modules/node-red/node_modules/clone/clone.js:162:18)
nodered.service: Main process exited, code=exited, status=1/FAILURE

I run NodeRed as part of Raspbian install. Was able to receive message ONCE, after that any message, crashes the NodeRed.
@madmax3365 madmax3365 added the V3 Marked issue will be fixed (resolved) in version 3 label Feb 26, 2021
@madmax3365
Copy link
Owner

Hey Alex.
I think one of the fields contains Promise.
When you forking output node the node-red fails to clone the message.
If that's your case, then it will be fixed in V3.
I'm currently working on it and planning to release it in a few days

@madmax3365
Copy link
Owner

Possible duplication of #1

@madmax3365 madmax3365 mentioned this issue Feb 26, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
V3 Marked issue will be fixed (resolved) in version 3
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@potatoronin @madmax3365