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.
Tenant used as key problem
See original GitHub issueThe TTenant is being used as the key to the concurrent dictionary here: https://github.com/saaskit/saaskit/blob/master/src/SaasKit.Multitenancy/Internal/TenantPipelineMiddleware.cs#L15
However, when the TenantContext is disposed (memory cache invalidation) the TTenant instance is disposed. However it’s still left as the key in the concurrent dictionary… Unclear if that will cause problems, but I am raising it as it seems undesirable?
Also there aren’t any constraints that I can see, that make it obvious to implementers of TTenant that they need to support being used a dictionary key. (implement GetHashCode, Equals etc))
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (1 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
…but now I’m seeing #68 and wondering if what I’m doing is such a good idea in light of the auto-disposal of properties. Could be a huge gotcha later. Hmmm. May need to fork.
I ended up using a
stringas myTTenantand put all the actual tenant config/settings into properties onTenantContext.