-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Losing Context with Async waterfall #55
Comments
+1 just stumbled upon this too using |
Update: false alarm in my case. Fixed it by requiring See #44 |
Thanks @mpseidel this lead to solving my issue as well.
|
Thanks! this saved my life just now. I've used express-http-context and express-jwt together. The latter uses async. |
Hello, does the async.waterfall have to be inside ns.run for it to work? |
The CLS context seems to be lost during async waterfall or series functions. It does appear to be working with parallel.
Tested with
node 5.0.0
andnode 5.3.0
cls 3.1.4
async 1.5.0
Here is a simple test I've setup which fails on the 2nd waterfall function, the context is available within the 1st waterfall function. Am I doing something incorrect or is there an issue here?
The text was updated successfully, but these errors were encountered: