dtoro
d4d99a7473
Problem: the hexagonal refactor churns the backend tree for nine more phases; the UI delivery stack (web/ SPA, cmd/desktop Wails wrapper, compose/web image) must move to its own repo first so doc/layout rewrites land once on a backend-only tree. Change: - New repo git.hubris.network/dtoro/oikos-web (v0.33.0): web/, desktop/ (updateURL repointed to oikos-web releases), compose/, own CI (web + desktop jobs), own deploy script (CI-green gate, TOCTOU guard, version-tagged images, prune-to-3), own webhook receiver on :9798 + launchd unit, own compose project publishing the same 8091:80. - Cutover executed on mac-mini in order: oikos stack's web service stopped+removed, oikos-web project brought up on 8091; outer Caddy untouched (targets the published port) — serving + Authentik flow + /wails 404 quirk verified post-cutover. - Stripped from oikos: web/, cmd/desktop/, compose/web/, desktop CI workflow, ci.yml web job, Makefile ui/desktop/desktop-package/install targets, the compose web service, oikos-web from deploy.sh's fallback prune list; wails + go-keyring dropped from go.mod, vendor synced. - README / CONTRIBUTING / AGENTS.md / .agents dev+operations docs now point at the new repo; mbse + mascot design docs carry a path note. Risk: production SPA serving depends on the new pipeline now; rollback is versioned-image re-up of the old web service from a pre-split checkout (port 8091). Desktop builds installed before the split still check dtoro/oikos releases — one manual reinstall, noted in the oikos-web release notes. Verification: go vet, make test (race), make generate-check, golangci (no new findings; baseline down 400→365); post-cutover curls — localhost:8091 200, /wails/runtime.js 404, outer Caddy 302 Authentik.
105 lines
2.5 KiB
Markdown
105 lines
2.5 KiB
Markdown
# why-is-node-running
|
|
|
|
Node is running but you don't know why? `why-is-node-running` is here to help you.
|
|
|
|
## Installation
|
|
|
|
Node 8 and above:
|
|
|
|
```bash
|
|
npm i why-is-node-running -g
|
|
```
|
|
|
|
Earlier Node versions (no longer supported):
|
|
|
|
```bash
|
|
npm i why-is-node-running@v1.x -g
|
|
```
|
|
|
|
## Usage
|
|
|
|
```js
|
|
const log = require('why-is-node-running') // should be your first require
|
|
const net = require('net')
|
|
|
|
function createServer () {
|
|
const server = net.createServer()
|
|
setInterval(function () {}, 1000)
|
|
server.listen(0)
|
|
}
|
|
|
|
createServer()
|
|
createServer()
|
|
|
|
setTimeout(function () {
|
|
log() // logs out active handles that are keeping node running
|
|
}, 100)
|
|
```
|
|
|
|
Save the file as `example.js`, then execute:
|
|
|
|
```bash
|
|
node ./example.js
|
|
```
|
|
|
|
Here's the output:
|
|
|
|
```
|
|
There are 5 handle(s) keeping the process running
|
|
|
|
# Timeout
|
|
/home/maf/dev/node_modules/why-is-node-running/example.js:6 - setInterval(function () {}, 1000)
|
|
/home/maf/dev/node_modules/why-is-node-running/example.js:10 - createServer()
|
|
|
|
# TCPSERVERWRAP
|
|
/home/maf/dev/node_modules/why-is-node-running/example.js:7 - server.listen(0)
|
|
/home/maf/dev/node_modules/why-is-node-running/example.js:10 - createServer()
|
|
|
|
# Timeout
|
|
/home/maf/dev/node_modules/why-is-node-running/example.js:6 - setInterval(function () {}, 1000)
|
|
/home/maf/dev/node_modules/why-is-node-running/example.js:11 - createServer()
|
|
|
|
# TCPSERVERWRAP
|
|
/home/maf/dev/node_modules/why-is-node-running/example.js:7 - server.listen(0)
|
|
/home/maf/dev/node_modules/why-is-node-running/example.js:11 - createServer()
|
|
|
|
# Timeout
|
|
/home/maf/dev/node_modules/why-is-node-running/example.js:13 - setTimeout(function () {
|
|
```
|
|
|
|
**Important Note!**
|
|
`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.
|
|
|
|
## CLI
|
|
|
|
You 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)
|
|
|
|
```bash
|
|
why-is-node-running /path/to/some/file.js
|
|
```
|
|
|
|
```
|
|
probing module /path/to/some/file.js
|
|
kill -SIGUSR1 31115 for logging
|
|
```
|
|
|
|
To trigger the log:
|
|
|
|
```
|
|
kill -SIGUSR1 31115
|
|
```
|
|
|
|
## Require CLI Option
|
|
|
|
You can also use the node `-r` option to include `why-is-node-running`:
|
|
|
|
```bash
|
|
node -r why-is-node-running/include /path/to/some/file.js
|
|
```
|
|
|
|
The steps are otherwise the same as the above CLI section
|
|
|
|
## License
|
|
|
|
MIT
|