@contrail/cli 3.4.5 → 3.4.6-alpha.cffb28e

package/node_modules/on-exit-leak-free/README.md

@@ -0,0 +1,54 @@
+# on-exit-leak-free
+
+This module helps dispose of an object gracefully when the Node.js process exits.
+It executes a function with a given parameter
+on [`'exit'`](https://nodejs.org/api/process.html#event-exit) without leaking memory,
+cleaning things up appropriately if the object is garbage collected.
+
+Requires `WeakRef` and `FinalizationRegistry`, i.e. use Node v14+.
+
+## Install
+
+```bash
+npm i on-exit-leak-free
+```
+
+## Example
+
+```js
+'use strict'
+
+const { register, unregister } = require('on-exit-leak-free')
+const assert = require('assert')
+
+function setup () {
+  // This object can be safely garbage collected,
+  // and the resulting shutdown function will not be called.
+  // There are no leaks.
+  const obj = { foo: 'bar' }
+  register(obj, shutdown)
+  // use registerBeforeExit(obj, shutdown) to execute the function only
+  // on beforeExit
+  // call unregister(obj) to remove
+}
+
+let shutdownCalled = false
+
+// Please make sure that the function passed to register()
+// does not create a closure around unnecessary objects.
+function shutdown (obj, eventName) {
+  console.log(eventName) // beforeExit
+  shutdownCalled = true
+  assert.strictEqual(obj.foo, 'bar')
+}
+
+setup()
+
+process.on('exit', function () {
+  assert.strictEqual(shutdownCalled, true)
+})
+```
+
+## License
+
+MIT

package/node_modules/on-exit-leak-free/index.js

@@ -0,0 +1,108 @@
+'use strict'
+
+const refs = {
+  exit: [],
+  beforeExit: []
+}
+const functions = {
+  exit: onExit,
+  beforeExit: onBeforeExit
+}
+
+let registry
+
+function ensureRegistry () {
+  if (registry === undefined) {
+    registry = new FinalizationRegistry(clear)
+  }
+}
+
+function install (event) {
+  if (refs[event].length > 0) {
+    return
+  }
+
+  process.on(event, functions[event])
+}
+
+function uninstall (event) {
+  if (refs[event].length > 0) {
+    return
+  }
+  process.removeListener(event, functions[event])
+  if (refs.exit.length === 0 && refs.beforeExit.length === 0) {
+    registry = undefined
+  }
+}
+
+function onExit () {
+  callRefs('exit')
+}
+
+function onBeforeExit () {
+  callRefs('beforeExit')
+}
+
+function callRefs (event) {
+  for (const ref of refs[event]) {
+    const obj = ref.deref()
+    const fn = ref.fn
+
+    // This should always happen, however GC is
+    // undeterministic so it might not happen.
+    /* istanbul ignore else */
+    if (obj !== undefined) {
+      fn(obj, event)
+    }
+  }
+  refs[event] = []
+}
+
+function clear (ref) {
+  for (const event of ['exit', 'beforeExit']) {
+    const index = refs[event].indexOf(ref)
+    refs[event].splice(index, index + 1)
+    uninstall(event)
+  }
+}
+
+function _register (event, obj, fn) {
+  if (obj === undefined) {
+    throw new Error('the object can\'t be undefined')
+  }
+  install(event)
+  const ref = new WeakRef(obj)
+  ref.fn = fn
+
+  ensureRegistry()
+  registry.register(obj, ref)
+  refs[event].push(ref)
+}
+
+function register (obj, fn) {
+  _register('exit', obj, fn)
+}
+
+function registerBeforeExit (obj, fn) {
+  _register('beforeExit', obj, fn)
+}
+
+function unregister (obj) {
+  if (registry === undefined) {
+    return
+  }
+  registry.unregister(obj)
+  for (const event of ['exit', 'beforeExit']) {
+    refs[event] = refs[event].filter((ref) => {
+      const _obj = ref.deref()
+      return _obj && _obj !== obj
+    })
+    uninstall(event)
+  }
+}
+
+module.exports = {
+  register,
+  registerBeforeExit,
+  unregister
+}

package/node_modules/on-exit-leak-free/package.json

@@ -0,0 +1,37 @@
+{
+  "name": "on-exit-leak-free",
+  "version": "2.1.2",
+  "description": "Execute a function on exit without leaking memory, allowing all objects to be garbage collected",
+  "main": "index.js",
+  "scripts": {
+    "test": "standard | snazzy && tap test/*.js"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/mcollina/on-exit-or-gc.git"
+  },
+  "keywords": [
+    "weak",
+    "reference",
+    "finalization",
+    "registry",
+    "process",
+    "exit",
+    "garbage",
+    "collector"
+  ],
+  "author": "Matteo Collina <hello@matteocollina.com>",
+  "license": "MIT",
+  "bugs": {
+    "url": "https://github.com/mcollina/on-exit-or-gc/issues"
+  },
+  "homepage": "https://github.com/mcollina/on-exit-or-gc#readme",
+  "devDependencies": {
+    "snazzy": "^9.0.0",
+    "standard": "^17.0.0",
+    "tap": "^16.0.0"
+  },
+  "engines": {
+    "node": ">=14.0.0"
+  }
+}

package/node_modules/on-exit-leak-free/test/base.test.js

@@ -0,0 +1,30 @@
+'use strict'
+
+const { test } = require('tap')
+const { fork } = require('child_process')
+const { join } = require('path')
+const { once } = require('events')
+const { register } = require('..')
+
+const files = [
+  'close.js',
+  'beforeExit',
+  'gc-not-close.js',
+  'unregister.js'
+]
+
+for (const file of files) {
+  test(file, async ({ equal }) => {
+    const child = fork(join(__dirname, 'fixtures', file), [], {
+      execArgv: ['--expose-gc']
+    })
+
+    const [code] = await once(child, 'close')
+
+    equal(code, 0)
+  })
+}
+
+test('undefined', async ({ throws }) => {
+  throws(() => register(undefined))
+})

package/node_modules/on-exit-leak-free/test/event-emitter-leak.test.js

@@ -0,0 +1,23 @@
+'use strict'
+
+const t = require('tap')
+const { register, unregister } = require('..')
+
+process.on('warning', () => {
+  t.fail('warning emitted')
+})
+
+const objs = []
+for (let i = 0; i < 20; i++) {
+  const obj = { i }
+  objs.push(obj)
+  register(obj, shutdown)
+}
+
+for (const obj of objs) {
+  unregister(obj)
+}
+
+t.pass('completed')
+
+function shutdown () {}

package/node_modules/on-exit-leak-free/test/fixtures/beforeExit.js

@@ -0,0 +1,33 @@
+'use strict'
+
+const { unregister, registerBeforeExit } = require('../..')
+const assert = require('assert')
+
+function setup () {
+  const obj = { foo: 'bar' }
+  registerBeforeExit(obj, shutdown)
+}
+
+let shutdownCalled = false
+let timeoutFinished = false
+function shutdown (obj, event) {
+  shutdownCalled = true
+  if (event === 'beforeExit') {
+    setTimeout(function () {
+      timeoutFinished = true
+      assert.strictEqual(obj.foo, 'bar')
+      unregister(obj)
+    }, 100)
+    process.on('beforeExit', function () {
+      assert.strictEqual(timeoutFinished, true)
+    })
+  } else {
+    throw new Error('different event')
+  }
+}
+
+setup()
+
+process.on('exit', function () {
+  assert.strictEqual(shutdownCalled, true)
+})

package/node_modules/on-exit-leak-free/test/fixtures/close.js

@@ -0,0 +1,21 @@
+'use strict'
+
+const { register } = require('../..')
+const assert = require('assert')
+
+function setup () {
+  const obj = { foo: 'bar' }
+  register(obj, shutdown)
+}
+
+let shutdownCalled = false
+function shutdown (obj) {
+  shutdownCalled = true
+  assert.strictEqual(obj.foo, 'bar')
+}
+
+setup()
+
+process.on('exit', function () {
+  assert.strictEqual(shutdownCalled, true)
+})

package/node_modules/on-exit-leak-free/test/fixtures/gc-not-close.js

@@ -0,0 +1,24 @@
+'use strict'
+
+const { register } = require('../..')
+const assert = require('assert')
+
+function setup () {
+  let obj = { foo: 'bar' }
+  register(obj, shutdown)
+  setImmediate(function () {
+    obj = undefined
+    gc() // eslint-disable-line
+  })
+}
+
+let shutdownCalled = false
+function shutdown (obj) {
+  shutdownCalled = true
+}
+
+setup()
+
+process.on('exit', function () {
+  assert.strictEqual(shutdownCalled, false)
+})

package/node_modules/on-exit-leak-free/test/fixtures/unregister.js

@@ -0,0 +1,24 @@
+'use strict'
+
+const { register, unregister } = require('../..')
+const assert = require('assert')
+
+function setup () {
+  const obj = { foo: 'bar' }
+  register(obj, shutdown)
+  setImmediate(function () {
+    unregister(obj)
+    unregister(obj) // twice, this should not throw
+  })
+}
+
+let shutdownCalled = false
+function shutdown (obj) {
+  shutdownCalled = true
+}
+
+setup()
+
+process.on('exit', function () {
+  assert.strictEqual(shutdownCalled, false)
+})

package/node_modules/pino/.prettierignore

@@ -0,0 +1 @@
+*

package/node_modules/pino/CNAME

@@ -0,0 +1 @@
+getpino.io

package/node_modules/pino/CONTRIBUTING.md

@@ -0,0 +1,30 @@
+# Pino is an OPEN Open Source Project
+
+## What?
+
+Individuals making significant and valuable contributions are given commit-access to the project to contribute as they see fit. This project is more like an open wiki than a standard guarded open source project.
+
+## Rules
+
+Before you start coding, please read [Contributing to projects with git](https://jrfom.com/posts/2017/03/08/a-primer-on-contributing-to-projects-with-git/). 
+
+Notice that as long as you don't have commit-access to the project, you have to fork the project and open PRs from the feature branches of the forked project.
+
+There are a few basic ground-rules for contributors:
+
+1. **No `--force` pushes** on `main` or modifying the Git history in any way after a PR has been merged.
+1. **Non-main branches** ought to be used for ongoing work.
+1. **Non-trivial changes** ought to be subject to an **internal pull-request** to solicit feedback from other contributors.
+1. All pull-requests for new features **must** target the `main` branch. PRs to fix bugs in LTS releases are also allowed.
+1. Contributors should attempt to adhere to the prevailing code-style.
+1. 100% code coverage
+
+## Releases
+
+Declaring formal releases remains the prerogative of the project maintainer.
+
+## Changes to this arrangement
+
+This is an experiment and feedback is welcome! This document may also be subject to pull-requests or changes by contributors where you believe you have something valuable to add or change.
+
+-----------------------------------------

package/node_modules/pino/LICENSE

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2016-2025 Matteo Collina, David Mark Clements and the Pino contributors listed at <https://github.com/pinojs/pino#the-team> and in the README file.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/node_modules/pino/README.md

@@ -0,0 +1,177 @@
+![banner](pino-banner.png)
+
+# pino
+[![npm version](https://img.shields.io/npm/v/pino)](https://www.npmjs.com/package/pino)
+[![Build Status](https://img.shields.io/github/actions/workflow/status/pinojs/pino/ci.yml)](https://github.com/pinojs/pino/actions)
+[![js-standard-style](https://img.shields.io/badge/code%20style-standard-brightgreen.svg?style=flat)](https://standardjs.com/)
+
+[Very low overhead](#low-overhead) JavaScript logger.
+
+## Documentation
+
+* [Benchmarks ⇗](/docs/benchmarks.md)
+* [API ⇗](/docs/api.md)
+* [Browser API ⇗](/docs/browser.md)
+* [Redaction ⇗](/docs/redaction.md)
+* [Child Loggers ⇗](/docs/child-loggers.md)
+* [Transports ⇗](/docs/transports.md)
+* [Diagnostics ⇗](/docs/diagnostics.md)
+* [Web Frameworks ⇗](/docs/web.md)
+* [Pretty Printing ⇗](/docs/pretty.md)
+* [Asynchronous Logging ⇗](/docs/asynchronous.md)
+* [Ecosystem ⇗](/docs/ecosystem.md)
+* [Help ⇗](/docs/help.md)
+* [Long Term Support Policy ⇗](/docs/lts.md)
+
+## Runtimes
+
+### Node.js
+
+Pino is built to run on [Node.js](http://nodejs.org).
+
+### Bare
+
+Pino works on [Bare](https://github.com/holepunchto/bare) with the [`pino-bare`](https://github.com/pinojs/pino-bare) compatability module.
+
+### Pear
+
+Pino works on [Pear](https://docs.pears.com), which is built on [Bare](https://github.com/holepunchto/bare), with the [`pino-bare`](https://github.com/pinojs/pino-bare) compatibility module.
+
+
+## Install
+
+Using NPM:
+```
+$ npm install pino
+```
+
+Using YARN:
+```
+$ yarn add pino
+```
+
+If you would like to install pino v6, refer to https://github.com/pinojs/pino/tree/v6.x.
+
+## Usage
+
+```js
+const logger = require('pino')()
+
+logger.info('hello world')
+
+const child = logger.child({ a: 'property' })
+child.info('hello child!')
+```
+
+This produces:
+
+```
+{"level":30,"time":1531171074631,"msg":"hello world","pid":657,"hostname":"Davids-MBP-3.fritz.box"}
+{"level":30,"time":1531171082399,"msg":"hello child!","pid":657,"hostname":"Davids-MBP-3.fritz.box","a":"property"}
+```
+
+For using Pino with a web framework see:
+
+* [Pino with Fastify](docs/web.md#fastify)
+* [Pino with Express](docs/web.md#express)
+* [Pino with Hapi](docs/web.md#hapi)
+* [Pino with Restify](docs/web.md#restify)
+* [Pino with Koa](docs/web.md#koa)
+* [Pino with Node core `http`](docs/web.md#http)
+* [Pino with Nest](docs/web.md#nest)
+* [Pino with Hono](docs/web.md#hono)
+
+<a name="essentials"></a>
+## Essentials
+
+### Development Formatting
+
+The [`pino-pretty`](https://github.com/pinojs/pino-pretty) module can be used to
+format logs during development:
+
+![pretty demo](pretty-demo.png)
+
+### Transports & Log Processing
+
+Due to Node's single-threaded event-loop, it's highly recommended that sending,
+alert triggering, reformatting, and all forms of log processing
+are conducted in a separate process or thread.
+
+In Pino terminology, we call all log processors "transports" and recommend that the
+transports be run in a worker thread using our `pino.transport` API.
+
+For more details see our [Transports⇗](docs/transports.md) document.
+
+### Low overhead
+
+Using minimum resources for logging is very important. Log messages
+tend to get added over time and this can lead to a throttling effect
+on applications – such as reduced requests per second.
+
+In many cases, Pino is over 5x faster than alternatives.
+
+See the [Benchmarks](docs/benchmarks.md) document for comparisons.
+
+### Bundling support
+
+Pino supports being bundled using tools like webpack or esbuild. 
+
+See [Bundling](docs/bundling.md) document for more information.
+
+<a name="team"></a>
+## The Team
+
+### Matteo Collina
+
+<https://github.com/mcollina>
+
+<https://www.npmjs.com/~matteo.collina>
+
+<https://twitter.com/matteocollina>
+
+### David Mark Clements
+
+<https://github.com/davidmarkclements>
+
+<https://www.npmjs.com/~davidmarkclements>
+
+<https://twitter.com/davidmarkclem>
+
+### James Sumners
+
+<https://github.com/jsumners>
+
+<https://www.npmjs.com/~jsumners>
+
+<https://twitter.com/jsumners79>
+
+### Thomas Watson Steen
+
+<https://github.com/watson>
+
+<https://www.npmjs.com/~watson>
+
+<https://twitter.com/wa7son>
+
+## Contributing
+
+Pino is an **OPEN Open Source Project**. This means that:
+
+> Individuals making significant and valuable contributions are given commit-access to the project to contribute as they see fit. This project is more like an open wiki than a standard guarded open source project.
+
+See the [CONTRIBUTING.md](https://github.com/pinojs/pino/blob/main/CONTRIBUTING.md) file for more details.
+
+<a name="acknowledgments"></a>
+## Acknowledgments
+
+This project was kindly sponsored by [nearForm](https://nearform.com).
+This project is kindly sponsored by [Platformatic](https://platformatic.dev).
+
+Logo and identity designed by Cosmic Fox Design: https://www.behance.net/cosmicfox.
+
+## License
+
+Licensed under [MIT](./LICENSE).
+
+[elasticsearch]: https://www.elastic.co/products/elasticsearch
+[kibana]: https://www.elastic.co/products/kibana

package/node_modules/pino/SECURITY.md

@@ -0,0 +1,87 @@
+# Security Policy
+
+This document describes the management of vulnerabilities for the
+Pino project and all modules within the Pino organization.
+
+## The Pino Threat Model
+
+Pino is a fast JSON logger for Node.js. Understanding what Pino considers
+a security vulnerability requires understanding its trust boundaries.
+
+Pino's threat model builds upon the
+[Node.js threat model](https://github.com/nodejs/node/blob/main/SECURITY.md#the-nodejs-threat-model).
+We recommend reading that document first, as Pino inherits its trust assumptions.
+
+Pino trusts the applications using it and the environment that it is running in.
+This includes all the application code, the transport, the filesystem and all
+non-externally provided input.
+
+Pino assumes all objects being logged, `logger.info(obj, message)`, are json-serializable.
+Use the `serializers` and `redact` features to sanitize them.
+
+Pino is not hardened against external prototype pollution attacks, but we
+will accept a vulnerability if Pino can be misused to cause a prototype pollution.
+
+## Reporting vulnerabilities
+
+Individuals who find potential vulnerabilities in Pino are invited
+to report them via email at matteo.collina@gmail.com.
+
+### Strict measures when reporting vulnerabilities
+
+Avoid creating new "informative" reports. Only create new
+report a potential vulnerability if you are absolutely sure this
+should be tagged as an actual vulnerability. Be careful on the maintainers time.
+
+## Handling vulnerability reports
+
+When a potential vulnerability is reported, the following actions are taken:
+
+### Triage
+
+**Delay:** 5 business days
+
+Within 5 business days, a member of the security team provides a first answer to the
+individual who submitted the potential vulnerability. The possible responses
+can be:
+
+* Acceptance: what was reported is considered as a new vulnerability
+* Rejection: what was reported is not considered as a new vulnerability
+* Need more information: the security team needs more information in order to evaluate what was reported.
+
+Triaging should include updating issue fields:
+* Asset - set/create the module affected by the report
+* Severity - TBD, currently left empty
+
+### Correction follow-up
+
+**Delay:** 90 days
+
+When a vulnerability is confirmed, a member of the security team volunteers to follow
+up on this report.
+
+With the help of the individual who reported the vulnerability, they contact
+the maintainers of the vulnerable package to make them aware of the
+vulnerability. The maintainers can be invited as participants to the reported issue.
+
+With the package maintainer, they define a release date for the publication
+of the vulnerability. Ideally, this release date should not happen before
+the package has been patched.
+
+The report's vulnerable versions upper limit should be set to:
+* `*` if there is no fixed version available by the time of publishing the report.
+* the last vulnerable version. For example: `<=1.2.3` if a fix exists in `1.2.4`
+
+### Publication
+
+**Delay:** 90 days
+
+Within 90 days after the triage date, the vulnerability must be made public.
+
+**Severity**: Vulnerability severity is assessed using [CVSS v.3](https://www.first.org/cvss/user-guide).
+
+If the package maintainer is actively developing a patch, an additional delay
+can be added with the approval of the security team and the individual who
+reported the vulnerability. 
+
+At this point, a CVE will be requested by the team.