[WIP] Deadlock when creating typed HttpClient with DI and HttpClientFactory #40740
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #35986
Perhaps a more general fix would be to correct the DI limitation for when a singleton instantiation required a transient that is to be lazily instantiated.
I am assuming here in order to just fix HttpClientFactory issue, that it is OK to get HttpMessageHandlerBuilder first hand in the constructor and whenever we want to lazily call CreateHandlerEntry, then the builder is already available (we basically move the GetRequiredService call out of lazy block to fix the deadlock.)
Then perhaps in 6.0 we could look to also fix the DI limitation that causes us to use this workaround.
cc: @davidfowl @tarekgh @eerhardt