Ednardo Teixeira
Ednardo Teixeira
Resolution: ` use(...) { if (!httpContext.ns.active) { let context = httpContext.ns.createContext(); httpContext.ns.context = context; httpContext.ns.active = context; } } `
@cupofjoakim It makes this instance in the creation of its initial context because this is an express-context bug. This is what I realized in debugging.
@cupofjoakim, this is only once. It's a hammer hehe
> Same issue here. Solved with @eteixeira94 patch (many thanks!), but should be solved in a better way. @jbaris, sorry I don't even know if this project is public to...
Sorry, I'm already using "httpContext.middleware" in the application, but it still has an error.  The error can be simulated when it is necessary to recover a value, for example,...
 @jbaris