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.
As described in #1446, the HTTP version of OmniSharp-roslyn does not log any output.
I managed to find the commit where the logging stopped working, it was 4f9fb4d by @DustinCampbell. In that commit the
HostHelpers.LogFilter()
functionality was refactored intoCompositionHostBuilder.CreateDefaultServiceProvider()
, which has aconfigureLogging
callback argument.The problem here is that in the HTTP
configureLogging
callback,ExceptionHandlerMiddleware
is included in a filter like this:This filter is applied on top of the filter already added in
CompositionHostBuilder.CreateDefaultServiceProvider()
, which looks like this:The simplest way I have found to ensure that the HTTP filter doesn't clobber the
CompositionHostBuilder
filter is to duplicate the entireCompositionHostBuilder
filter in the HTTP code:This is not a very clean solution so please let me know if there's a tidier way to do this.
Fixes #1446