node-continuation-local-storage
node-continuation-local-storage copied to clipboard
othiym23
implementation of https://github.com/joyent/node/issues/5243
In a single project there may be - multiple versions of Promise implementation, say `bluebird@2`, `bluebird@1` - multiple packages of Promise implementation, say coexistence of `bluebird` and `Q`. All these...
This is a continuation of #75 to add a test.
I'm using the latest elasticsearch client (v11.0.1) and am running into issues with losing context. With a small number of concurrent requests, it works fine. However, as the load increases...
This happens in the case of uncaught errors in nested contexts (which are sometimes created by Mongoose, etc). The nested context rethrows the error in its catch block after attaching...
If the code uses `bindEmitter`, and the emitter triggers after `context.exit()`, should the emitter work? For example, the code: ``` js app.use(function*(next) { var context = ns.createContext(); ns.enter(context); ns.bindEmitter(this.req); ns.bindEmitter(this.res);...
The code below uses `bindEmitter` to bind the response object to the current context. So `onfinish` must keep the context, right? ``` js // bind process.namespaces.app.bindEmitter(this.res); // plan onfinish in...
Hi Forrest, First of all, in my view cls is a wonderful peace of software. I just started using it and it solves lots of issues for me. Thank you...
Just as an FYI, we're in the process of migrating from `Q` to `bluebird` so a new shim was needed. I did a quick port from `cls-q`, only adapting the...
use CLS to save session data, but found that session is chaos.  
If I modify net-events.tap.js to have the server do socket.destroy() rather than a socket.end(), I get a 'close' event in the client that does not get the client.write cls. Should...
