Brunobkr/llama.cpp_AlgMor24_github

1# why-is-node-running2 3Node is running but you don't know why? `why-is-node-running` is here to help you.4 5## Installation6 7Node 8 and above:8 9```bash10npm i why-is-node-running -g11```12 13Earlier Node versions (no longer supported):14 15```bash16npm i why-is-node-running@v1.x -g17```18 19## Usage20 21```js22const log = require('why-is-node-running') // should be your first require23const net = require('net')24 25function createServer () {26  const server = net.createServer()27  setInterval(function () {}, 1000)28  server.listen(0)29}30 31createServer()32createServer()33 34setTimeout(function () {35  log() // logs out active handles that are keeping node running36}, 100)37```38 39Save the file as `example.js`, then execute:40 41```bash42node ./example.js43```44 45Here's the output:46 47```48There are 5 handle(s) keeping the process running49 50# Timeout51/home/maf/dev/node_modules/why-is-node-running/example.js:6  - setInterval(function () {}, 1000)52/home/maf/dev/node_modules/why-is-node-running/example.js:10 - createServer()53 54# TCPSERVERWRAP55/home/maf/dev/node_modules/why-is-node-running/example.js:7  - server.listen(0)56/home/maf/dev/node_modules/why-is-node-running/example.js:10 - createServer()57 58# Timeout59/home/maf/dev/node_modules/why-is-node-running/example.js:6  - setInterval(function () {}, 1000)60/home/maf/dev/node_modules/why-is-node-running/example.js:11 - createServer()61 62# TCPSERVERWRAP63/home/maf/dev/node_modules/why-is-node-running/example.js:7  - server.listen(0)64/home/maf/dev/node_modules/why-is-node-running/example.js:11 - createServer()65 66# Timeout67/home/maf/dev/node_modules/why-is-node-running/example.js:13 - setTimeout(function () {68```69 70**Important Note!**71`unref`ed timers do not prevent the Node process from exiting. If you are running with Node v11.0.0 and above, `unref`ed timers will not be listed in the above list. Unfortunately, this is not supported in node versions below v11.0.0.72 73## CLI74 75You can also run `why-is-node-running` as a standalone if you don't want to include it inside your code. Sending `SIGUSR1`/`SIGINFO` signal to the process will produce the log. (`Ctrl + T` on macOS and BSD systems)76 77```bash78why-is-node-running /path/to/some/file.js79```80 81```82probing module /path/to/some/file.js83kill -SIGUSR1 31115 for logging84```85 86To trigger the log:87 88```89kill -SIGUSR1 3111590```91 92## Require CLI Option93 94You can also use the node `-r` option to include `why-is-node-running`:95 96```bash97node -r why-is-node-running/include /path/to/some/file.js98```99 100The steps are otherwise the same as the above CLI section101 102## License103 104MIT105