node-red / node-red/node-red-nodes
node-red-node-mysql throw uncaught exception
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 612
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 3
Description
Hi !
Randomly i got a unhandled exception form mysql node. Here is what i got from console:
27 Feb 16:31:45 - [red] Uncaught Exception:
27 Feb 16:31:45 - Error: Connection lost: The server closed the connection.
at Protocol.end (C:\Users\tamas.node-red\node modules\mysql\lib\protocol\Protocol.js:112:13)
at Socket.tanonymoust (C:\Users\tamas.node-red\node modules\mysql\lib\Connection.js:94:20
at Socket. (C:\Users\tamas.node-red\node modules\mysql\lib\Connection.js:526:10)
at Socket.emit (events.js:326:22)
at endReadableNT (_stream_readable.js:1223:12)
at processTicksAndRejections (internal/process/task queues.js:84:21)
Can you help me?
- Node-RED version: 1.2.7
- node.js version: v12.19.0
- npm version: 6.14.8
- Platform/OS: Windows_NT 10.0.19042 x64 LE
- Browser: chrome 88.0.4324.190 64 bit
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 reported stack trace in the mysql package, especially Protocol.js and Connection.js, and reproduce the connection-loss scenario using the listed Node-RED, Node.js, and Windows versions. Determine how node-red-node-mysql handles the server closing the connection; done means the failure no longer becomes an uncaught exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, mysql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100