-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 currentContext after installing Newrelic agent #1984
Comments
+1 |
hey @olivierl do you get the error from postgresql only or from the default db as well? |
hi @jannyHou, I've made the test with the default db (memory) and it's worst, |
Thanks @olivierl I reproduced your error. When I hit the endpoint
We will look into the problem! One more question, I am not so familiar with |
+1 |
Thank you @esopian @andressrg for reporting this, we will take a look. One more question for better debug: are you also getting this error with newrelic or even without using newrelic? |
could be same origin as #1807 |
+1 |
1 similar comment
+1 |
+1 |
-1 |
+1 |
Hi, loopback-context is know to loose the context in many cases. We have deprecated it in favour of explicit context passing via the "options" argument, see #1495. There is also an alternative approach being explored in https://github.com/strongloop/loopback-context, feel free to give it a try. If you do, then please report any issues found in loopback-context's issue tracker. I am closing this issue. |
When I add Newrelic agent on top of the server.js, the currentContext "lose" the accessToken in my operation hook...
Check this sandbox
server/server.js
common/models/customer.js
package.json
The text was updated successfully, but these errors were encountered: