TypeError: Object #<Client> has no method 'destroy'
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
$ sudo npm install node.uptime -g
/usr/local/bin/node.uptime -> /usr/local/lib/node_modules/node.uptime/bin/node.uptime
node.uptime@0.1.0 /usr/local/lib/node_modules/node.uptime
└── optimist@0.3.1
$ node.uptime -h github.com -u "echo up" -d "echo down"
/usr/local/lib/node_modules/node.uptime/lib/node.uptime/index.js:54
client.destroy();
^
TypeError: Object # has no method 'destroy'
at IncomingMessage. (/usr/local/lib/node_modules/node.uptime/lib/node.uptime/index.js:54:16)
at IncomingMessage.emit (events.js:88:20)
at HTTPParser.onMessageComplete (http.js:137:23)
at Socket.ondata (http.js:1124:24)
at TCP.onread (net.js:349:27)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the reported command and inspect lib/node.uptime/index.js at line 54, where client.destroy() raises the TypeError. Trace how the Client is created and used around the HTTP response callback. Done means the command completes without this exception and the reported up/down behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100