Hey @Callum-OKane it does indeed look like memwatch-next isn’t building properly. I’ll try to take a look when I have a few minutes; figuring that out is probably what’s required to get rid of that error.
Ok, it seems like node-memwatch is incompatible with Node v9+ based on some of the issues on the GitHub repo. If you set your Node version to "node": "8.15.0" I think node-gyp will be able to compile memwatch-next. You might need an enable-pnpm to make sure the install proceeds properly.
Since this was a different problem than the previous topic, I’ve moved it to a new topic.
(node:1381) UnhandledPromiseRejectionWarning: Error: connect ETIMEDOUT 104.16.58.5:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
(node:1381) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 5)
(node:1381) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:1381) UnhandledPromiseRejectionWarning: Error: connect ETIMEDOUT 104.16.58.5:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
(node:1381) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 6)
(node:1381) UnhandledPromiseRejectionWarning: Error: connect ETIMEDOUT 104.16.59.5:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
(node:1381) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 7)
(node:1381) UnhandledPromiseRejectionWarning: Error: connect ETIMEDOUT 104.16.58.5:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
(node:1381) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 8)
(node:1381) UnhandledPromiseRejectionWarning: Error: connect ETIMEDOUT 104.16.59.5:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
(node:1381) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 9)
(node:1381) UnhandledPromiseRejectionWarning: Error: connect ETIMEDOUT 104.16.58.5:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
(node:1381) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 10)
(node:1381) UnhandledPromiseRejectionWarning: Error: connect ETIMEDOUT 104.16.59.5:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
(node:1381) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 11)
(node:1381) UnhandledPromiseRejectionWarning: Error: connect ETIMEDOUT 104.16.58.5:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
(node:1381) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 12)
(node:1381) UnhandledPromiseRejectionWarning: Error: connect ETIMEDOUT 104.16.58.5:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
(node:1381) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 13)
(node:1381) UnhandledPromiseRejectionWarning: Error: connect ETIMEDOUT 104.16.59.5:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
(node:1381) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 14)
(node:1381) UnhandledPromiseRejectionWarning: Error: connect ETIMEDOUT 104.16.58.5:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
(node:1381) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 15)
(node:1381) UnhandledPromiseRejectionWarning: Error: connect ETIMEDOUT 104.16.59.5:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
(node:1381) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 16)
(node:1381) UnhandledPromiseRejectionWarning: Error: connect ETIMEDOUT 104.16.59.5:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
(node:1381) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 17)
(node:1381) UnhandledPromiseRejectionWarning: Error: connect ETIMEDOUT 104.16.58.5:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
(node:1381) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 18)
(node:1381) UnhandledPromiseRejectionWarning: Error: connect ETIMEDOUT 104.16.59.5:443
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
(node:1381) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 19)
Hey @Callum-OKane in depth analysis of a problem like this is something you’ll need to tackle; it’s not something we’re able to commit to investigating.
That said, what I think you’ll want to do next if you’re going to dig into the details is to use memwatch-next’s Heap Diffs around different operations your bot is doing to try to isolate the actually leaking code.