@banumeow/n8n-nodes-oci-generativeai-agent 0.1.4 → 0.1.6

package/node_modules/oci-common/node_modules/opossum/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "{}"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright {yyyy} {name of copyright owner}
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/node_modules/oci-common/node_modules/opossum/README.md

@@ -0,0 +1,273 @@
+# opossum [![CircleCI](https://circleci.com/gh/nodeshift/opossum/tree/master.svg?style=svg&circle-token=0742302baa8c95cef354997ea52a383d3d078ff1)](https://circleci.com/gh/nodeshift/opossum/tree/master)
+
+[![Codacy Badge](https://api.codacy.com/project/badge/Grade/03f9af1e697743edbe91f8d29831a75d)](https://www.codacy.com/app/nodeshift/opossum?utm_source=github.com&utm_medium=referral&utm_content=nodeshift/opossum&utm_campaign=Badge_Grade)
+[![Codacy Badge](https://api.codacy.com/project/badge/Coverage/03f9af1e697743edbe91f8d29831a75d)](https://www.codacy.com/app/nodeshift/opossum?utm_source=github.com&utm_medium=referral&utm_content=nodeshift/opossum&utm_campaign=Badge_Coverage)
+[![Greenkeeper badge](https://badges.greenkeeper.io/nodeshift/opossum.svg)](https://greenkeeper.io/)
+[![Known Vulnerabilities](https://snyk.io/test/npm/opossum/badge.svg)](https://snyk.io/test/npm/opossum)
+[![dependencies Status](https://david-dm.org/nodeshift/opossum/status.svg)](https://david-dm.org/nodeshift/opossum)
+
+[![NPM](https://nodei.co/npm/opossum.png)](https://npmjs.org/package/opossum)
+
+Opossum is a Node.js circuit breaker that executes asynchronous functions
+and monitors their execution status. When things start failing, `opossum`
+plays dead and fails fast. If you want, you can provide a fallback function
+to be executed when in the failure state.
+
+For more about the circuit breaker pattern, there are lots of resources
+on the web - search it! Fowler's blog post is one place to
+[start reading](http://martinfowler.com/bliki/CircuitBreaker.html).
+
+|                 | Project Info  |
+| --------------- | ------------- |
+| License:        | Apache-2.0  |
+| Documentation:  | https://nodeshift.dev/opossum/ |
+| Typings:        | https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/opossum
+| Issue tracker:  | https://github.com/nodeshift/opossum/issues  |
+| Engines:        | Node.js >= 10 |
+
+## Usage
+
+Let's say you've got an API that depends on something that might fail -
+a network operation, or disk read, for example. Wrap those functions up in a
+`CircuitBreaker` and you have control over your destiny.
+
+```javascript
+const CircuitBreaker = require('opossum');
+
+function asyncFunctionThatCouldFail (x, y) {
+  return new Promise((resolve, reject) => {
+    // Do something, maybe on the network or a disk
+  });
+}
+
+const options = {
+  timeout: 3000, // If our function takes longer than 3 seconds, trigger a failure
+  errorThresholdPercentage: 50, // When 50% of requests fail, trip the circuit
+  resetTimeout: 30000 // After 30 seconds, try again.
+};
+const breaker = new CircuitBreaker(asyncFunctionThatCouldFail, options);
+
+breaker.fire(params)
+  .then(console.log)
+  .catch(console.error);
+```
+
+### Fallback
+
+You can also provide a fallback function that will be executed in the
+event of failure. To take some action when the fallback is performed,
+listen for the `fallback` event.
+
+```javascript
+const breaker = new CircuitBreaker(asyncFunctionThatCouldFail, options);
+// if asyncFunctionThatCouldFail starts to fail, firing the breaker
+// will trigger our fallback function
+breaker.fallback(() => 'Sorry, out of service right now');
+breaker.on('fallback', (result) => reportFallbackEvent(result));
+```
+
+Once the circuit has opened, a timeout is set based on `options.resetTimeout`.
+When the `resetTimeout` expires, `opossum` will enter the `halfOpen` state.
+Once in the `halfOpen` state, the next time the circuit is fired, the circuit's
+action will be executed again. If successful, the circuit will close and emit
+the `close` event. If the action fails or times out, it immediately re-enters
+the `open` state.
+
+When a fallback function is triggered, it's considered a failure, and the
+fallback function will continue to be executed until the breaker is closed.
+
+### Browser
+
+Opossum really shines in a browser. You can use it to guard against network
+failures in your AJAX calls.
+
+We recommend using [webpack](https://webpack.js.org/) to bundle your applications,
+since it does not have the effect of polluting the `window` object with a global.
+However, if you need it, you can access a `circuitBreaker` function in the global
+namespace by doing something similar to what is shown in the below example.
+
+Here is an example using [hapi.js](https://hapijs.com). See the
+[opossum-examples](https://github.com/nodeshift-starters/opossum-examples/)
+repository for more detail.
+
+Include `opossum.js` in your HTML file.
+
+```html
+<html>
+<head>
+  <title>My Super App</title>
+  <script type='text/javascript' src="/jquery.js"></script>
+  <script type='text/javascript' src="/opossum.js"></script>
+  <script type='text/javascript' src="/app.js"></script>
+<body>
+...
+</body>
+</head>
+</html>
+```
+
+In your application, set a route to the file, pointing to
+`node_modules/opossum/dist/opossum-min.js`.
+
+```js
+// server.js
+const server = new Hapi.Server();
+server.register(require('inert', (err) => possibleError(err)));
+server.route({
+  method: 'GET',
+  path: '/opossum.js',
+  handler: {
+    file: {
+      path: path.join(__dirname, 'node_modules', 'opossum', 'dist', 'opossum-min.js'),
+    }
+  }
+});
+```
+In the browser's global scope will be a `CircuitBreaker` constructor. Use it
+to create circuit breakers, guarding against network failures in your REST
+API calls.
+
+```js
+// app.js
+const route = 'https://example-service.com/rest/route';
+const circuitBreakerOptions = {
+  timeout: 500,
+  maxFailures: 3,
+  resetTimeout: 5000
+};
+
+const circuit = new CircuitBreaker(() => $.get(route), circuitBreakerOptions);
+circuit.fallback(() => `${route} unavailable right now. Try later.`));
+circuit.on('success', (result) => $(element).append(JSON.stringify(result)}));
+
+$(() => {
+  $('#serviceButton').click(() => circuit.fire().catch((e) => console.error(e)));
+});
+
+```
+
+### Events
+
+A `CircuitBreaker` will emit events for important things that occur.
+Here are the events you can listen for.
+
+  * `fire` - emitted when the breaker is fired.
+  * `reject` - emitted when the breaker is open (or halfOpen).
+  * `timeout` - emitted when the breaker action times out.
+  * `success` - emitted when the breaker action completes successfully
+  * `failure` - emitted when the breaker action fails, called with the error
+  * `open` - emitted when the breaker state changes to `open`
+  * `close` - emitted when the breaker state changes to `closed`
+  * `halfOpen` - emitted when the breaker state changes to `halfOpen`
+  * `fallback` - emitted when the breaker has a fallback function and executes it
+  * `semaphoreLocked` - emitted when the breaker is at capacity and cannot execute the request
+  * `healthCheckFailed` - emitted when a user-supplied health check function returns a rejected promise
+
+Handling events gives a greater level of control over your application behavior.
+
+```js
+const circuit = new CircuitBreaker(() => $.get(route), circuitBreakerOptions);
+
+circuit.fallback(() => ({ body: `${route} unavailable right now. Try later.` }));
+
+circuit.on('success',
+  (result) => $(element).append(
+    makeNode(`SUCCESS: ${JSON.stringify(result)}`)));
+
+circuit.on('timeout',
+  () => $(element).append(
+    makeNode(`TIMEOUT: ${route} is taking too long to respond.`)));
+
+circuit.on('reject',
+  () => $(element).append(
+    makeNode(`REJECTED: The breaker for ${route} is open. Failing fast.`)));
+
+circuit.on('open',
+  () => $(element).append(
+    makeNode(`OPEN: The breaker for ${route} just opened.`)));
+
+circuit.on('halfOpen',
+  () => $(element).append(
+    makeNode(`HALF_OPEN: The breaker for ${route} is half open.`)));
+
+circuit.on('close',
+  () => $(element).append(
+    makeNode(`CLOSE: The breaker for ${route} has closed. Service OK.`)));
+
+circuit.on('fallback',
+  (data) => $(element).append(
+    makeNode(`FALLBACK: ${JSON.stringify(data)}`)));
+```
+
+
+### Promises vs. Callbacks
+The `opossum` API returns a `Promise` from `CircuitBreaker.fire()`.
+But your circuit action - the async function that might fail -
+doesn't have to return a promise. You can easily turn Node.js style
+callback functions into something `opossum` understands by using the built in
+Node core utility function `util.promisify()` .
+
+```javascript
+const fs = require('fs');
+const { promisify } = require('util');
+const CircuitBreaker = require('opossum');
+
+const readFile = promisify(fs.readFile);
+const breaker = new CircuitBreaker(readFile, options);
+
+breaker.fire('./package.json', 'utf-8')
+  .then(console.log)
+  .catch(console.error);
+```
+
+And just for fun, your circuit doesn't even really have to be a function.
+Not sure when you'd use this - but you could if you wanted to.
+
+```javascript
+const breaker = new CircuitBreaker('foo', options);
+
+breaker.fire()
+  .then(console.log) // logs 'foo'
+  .catch(console.error);
+```
+
+### Typings
+
+Typings are available [here](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/opossum).
+
+If you'd like to add them, run `npm install @types/opossum` in your project.
+
+### Metrics
+
+#### Prometheus
+The [`opossum-prometheus`](https://github.com/nodeshift/opossum-prometheus) module
+can be used to produce metrics that are consumable by Prometheus.
+These metrics include information about the circuit itself, for example how many
+times it has opened, as well as general Node.js statistics, for example event loop lag.
+
+
+#### Hystrix
+The [`opossum-hystrix`](https://github.com/nodeshift/opossum-hystrix) module can
+be used to produce metrics that are consumable by the Hystrix Dashboard.
+
+## Troubleshooting
+
+You may run into issues related to too many listeners on an `EventEmitter` like this.
+
+```sh
+(node:25619) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 10 unpipe listeners added. Use emitter.setMaxListeners() to increase limit
+(node:25619) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 drain listeners added. Use emitter.setMaxListeners() to increase limit
+(node:25619) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
+(node:25619) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added. Use emitter.setMaxListeners() to increase limit
+(node:25619) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 finish listeners added. Use emitter.setMaxListeners() to increase limit
+```
+
+In some cases, seeing this error might indicate a bug in client code, where many `CircuitBreaker`s are inadvertently being created. But there are legitimate scenarios where this may not be the case. For example, it could just be that you need more than 10 `CircuitBreaker`s in your app. That's ok.
+
+To get around the error, you can set the number of listeners on the stream.
+
+```js
+circuit.stats.getHystrixStream().setMaxListeners(100);
+```
+
+Or it could be that you have a large test suite which exercises some code that creates `CircuitBreaker`s and does so repeatedly. If the `CircuitBreaker` being created is only needed for the duration of the test, use `circuit.shutdown()` when the circuit is no longer in use to clean up all listeners.