natterstefan
commented
5 years ago Hi @RamboRogers,
thank you for the report. It is most likely that cp.exec (eg. https://github.com/DylanPiercey/local-devices/blob/master/src/index.js#L78, also reading https://stackoverflow.com/q/23429499/1238150, https://github.com/nicojs/node-install-local/issues/8 and https://github.com/lerna/lerna/issues/213#issuecomment-225657709) caused the issue.
Would you mind attaching/sending us a link with the anonymized output of the arp table output? Or at least the number of rows? I would really like to test this and act accordingly.
RamboRogers
I'm getting the following error when running find() on airport wifi. Works awesome at home/work.
I tried to wrap the find in try/catch and same error. Looking at the arp table I'm getting a lot of blank Mac addresses. Wonder if this could cause this error?
(node:68247) UnhandledPromiseRejectionWarning: RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER]: stdout maxBuffer length exceeded at Socket.onChildStdout (child_process.js:357:14) at Socket.emit (events.js:197:13) at addChunk (_stream_readable.js:288:12) at readableAddChunk (_stream_readable.js:265:13) at Socket.Readable.push (_stream_readable.js:224:10) at Pipe.onStreamRead (internal/stream_base_commons.js:145:17) (node:68247) 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: 1) (node:68247) [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.