You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Update async to version ^2.0.0 to prevent continuation-local-storage from loosing active context #2541
Part of the problems with Loopback context is because async and continuation-local-storage are used together under the hood. These two modules are known to have issues when used together.
@marlonkjoseph Your premises are correct, but upgrading all modules in node_modules includingloopback to async v2.0.0 did not solve the issue for me. Instead, I had more success with Node v6.3.1 and my own PR strongloop/loopback-context#2 locally, and I believe that it works thanks to its async-hook deep dependency (which requires a recent version of Node), but I need some more tests to be sure.
Activity
davidcheung commentedon Aug 3, 2016
@marlonkjoseph thanks for your suggestion! good call
https://github.com/strongloop/loopback/pull/2577/files
josieusa commentedon Aug 4, 2016
@marlonkjoseph Your premises are correct, but upgrading all modules in node_modules including
loopbacktoasyncv2.0.0 did not solve the issue for me. Instead, I had more success with Node v6.3.1 and my own PR strongloop/loopback-context#2 locally, and I believe that it works thanks to itsasync-hookdeep dependency (which requires a recent version of Node), but I need some more tests to be sure.davidcheung commentedon Aug 4, 2016
thanks @josieusa
Closing this issue, I think discussion would be easier to keep track on the loopback-context side