I’m going to mark this as a bug for now because it could have something to do with transition to .NET Core recently.