madmax3365 / madmax3365/node-red-node-discord
On message receive - Uncaught Exception: TypeError: Cannot assign to read only property 'writeQueueSize' of object '#<TCP>'
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
```
TypeError: Cannot assign to read only property 'writeQueueSize' of object '#'
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.
Contributor guide
No contributing guide indexed for this repository
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 by reproducing the crash after the first successfully received message and review the reported stack trace in /usr/lib/node_modules/node-red/node_modules/clone/clone.js, especially the _clone calls. Check the nodered.service failure behavior and consider the issue resolved when subsequent messages no longer terminate Node-RED.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100