Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Scoped Dependency Issue
See original GitHub issueThis issue may prove tricky to repro, so I’ll explain the issue and you can advise on further action.
This image shows some logs containing the HttpContext TraceIdentifier, the DbContext Id and a Guid in a scoped dependency RequestAuthVariables.
The highlighted rows show that two different HttpContexts get the same instance of RequestAuthVariables.
This is an intermittent issue in our production system and we’ve been able to reproduce in an integration test using a Parallel.ForEachAsync loop of 100. A loop of 10 typically works correctly and even the loop of 100 occasionally works.
Our interim solution is to register our triggers as Transient instead of Scoped.
We’re using the AddTriggeredDbContextPool and AddTriggeredPooledDbContextFactory
@benmccallum and I are happy to try and work with you as needed.
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:12 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I did report a potential regression on the pr about 30 mins ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.