Currently if you return T in an action that returns ActionResult<T> it will create an ObjectResult. The problem is that the StatusCode remains null rather than 200, even though the eventual response generated from it will be 200.

This makes it confusing in, for example, an action filter, where a developer may only want to handle Ok object results on the executed context, including where `

We can build much smaller Mono runtime for .NET Core purposes by simply removing code we don't need in this configuration. We did a few easy initial steps but we can go much further.

This list is not comprehensive but parts like

• Culture Data
• Any PAL related code
• Unused icalls

Describe the bug
Jellyfin and/or ffmpeg may fail on extracting subtitles. When this happens, a 0 KB srt file is saved but Jellyfin seems unable to remove it. Upon trying to play the video again, Jellyfin seems content that it has a 0KB SRT file, thus not playing any subtitles.

System (please complete the following information):

• OS: Windows 10 ver 1909
• Virtualization: None
• C

As mentioned by Diego, these additions would help by simplifying the API usage for users even further and it should be pretty easy to implement for us: 👍

@divega commented: dotnet/machinelearning-samples#617 (review)

@CESARDELATORRE, I did a deferred review. The experience seems pretty good.

1:
And I agree with you that it could be even better

Whenever I submit a GET request to the api/public/groups endpoint, the "collections" field for each group returns "None" on every group, even if they have access to collections. I can verify that the

The Job and Toolchain columns are redundant, Runtime is all we need:

I see this very often when our users are presenting BDN results at conferences|meetups etc

The Job column should remain visible when the user has set the Job id in explicit way.

/cc @stephentoub

Expected Behavior / New Feature

Support sticky sessions for ServiceDiscoveryProviders

Actual Behavior / Motivation for New Feature

When using websockets with ocelot in a distributed system, problem can arise since ocelot, as far as i know, doesn't support sticky sessions when working with service discovery providers.

The functionality could be great if it could work with both consul