sidorares / sidorares/node-mysql2
missing end/close events on connection object
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.4k
- Forks
- 680
- Avg merge
- 9h 7m
- Merged PRs (30d)
- 59
Description
I noticed at some point mysql2 stopped emitting important events on the connection object, namely end and/or close. This happens whether or not there was an error that caused the disconnection.
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
No file, test, or entry point is named in the issue. Start by tracing the connection lifecycle and disconnection handling in node-mysql2, covering both error and non-error disconnects. Done means the connection object emits the expected end and/or close events in each relevant case, with tests demonstrating the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql, node.js, typescript
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100