You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 5, 2019. It is now read-only.
I upgraded to Node 0.12.6, and begun getting the following error on the first request to Kloudless web api:
throw new TypeError('msecs must be a number');
^
TypeError: msecs must be a number
at Object.exports.enroll (timers.js:165:11)
at TLSSocket.Socket.setTimeout (net.js:337:12)
at ClientRequest. (_http_client.js:565:10)
at ClientRequest.g (events.js:199:16)
at ClientRequest.emit (events.js:129:20)
at tickOnSocket (_http_client.js:493:7)
at _http_client.js:504:7
at process._tickDomainCallback (node.js:381:11)
After investigation, it seems there was a default value on the msec parameter of the setTimeout function on the previous version of node (0.10), which has disappeared.
I fixed this temporarily on line 21 of kloudless.js (added the timeout property):
I upgraded to Node 0.12.6, and begun getting the following error on the first request to Kloudless web api:
TypeError: msecs must be a number
at Object.exports.enroll (timers.js:165:11)
at TLSSocket.Socket.setTimeout (net.js:337:12)
at ClientRequest. (_http_client.js:565:10)
at ClientRequest.g (events.js:199:16)
at ClientRequest.emit (events.js:129:20)
at tickOnSocket (_http_client.js:493:7)
at _http_client.js:504:7
at process._tickDomainCallback (node.js:381:11)
After investigation, it seems there was a default value on the msec parameter of the setTimeout function on the previous version of node (0.10), which has disappeared.
I fixed this temporarily on line 21 of kloudless.js (added the timeout property):
Could we get a better fix ?
The text was updated successfully, but these errors were encountered: