[master] Update dependencies from 4 repositories

[dotnet-maestro]

This pull request updates the following dependencies

From https://github.com/aspnet/EntityFrameworkCore

• Build: 20191217.1
• Date Produced: 12/17/2019 7:26 PM
• Commit: 16a6c3c57db2c77713cc5bbad2aad65c0d628d4a
• Branch: refs/heads/master
• Updates:
  • Microsoft.EntityFrameworkCore.Tools -> 5.0.0-alpha.1.19617.1
  • Microsoft.EntityFrameworkCore.SqlServer -> 5.0.0-alpha.1.19617.1
  • dotnet-ef -> 5.0.0-alpha.1.19617.1
  • Microsoft.EntityFrameworkCore -> 5.0.0-alpha.1.19617.1
  • Microsoft.EntityFrameworkCore.InMemory -> 5.0.0-alpha.1.19617.1
  • Microsoft.EntityFrameworkCore.Relational -> 5.0.0-alpha.1.19617.1
  • Microsoft.EntityFrameworkCore.Sqlite -> 5.0.0-alpha.1.19617.1

From https://github.com/aspnet/AspNetCore-Tooling

• Build: 20191218.1
• Date Produced: 12/18/2019 11:13 PM
• Commit: 998b14def40e40f2de214800ab8f1e3df1bb453f
• Branch: refs/heads/master
• Updates:
  • Microsoft.AspNetCore.Mvc.Razor.Extensions -> 5.0.0-alpha.1.19618.1
  • Microsoft.AspNetCore.Razor.Language -> 5.0.0-alpha.1.19618.1
  • Microsoft.CodeAnalysis.Razor -> 5.0.0-alpha.1.19618.1
  • Microsoft.NET.Sdk.Razor -> 5.0.0-alpha.1.19618.1

From https://github.com/aspnet/Blazor

• Build: 20191126.1
• Date Produced: 11/26/2019 5:51 PM
• Commit: d1f3a3db8a379cc887cd6dde0acf77dcd5e16c36
• Branch: refs/heads/master
• Updates:
  • Microsoft.AspNetCore.Blazor.Mono -> 3.1.0-preview4.19576.1

Coherency Updates

The following updates ensure that dependencies with a CoherentParentDependency
attribute were produced in a build used as input to the parent dependency's build.
See Dependency Description Format

• Microsoft.AspNetCore.Analyzer.Testing -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.AspNetCore.BenchmarkRunner.Sources -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.ActivatorUtilities.Sources -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Caching.Abstractions -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Caching.Memory -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Caching.SqlServer -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Caching.StackExchangeRedis -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.CommandLineUtils.Sources -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Configuration.Abstractions -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Configuration.AzureKeyVault -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Configuration.Binder -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Configuration.CommandLine -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Configuration.EnvironmentVariables -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Configuration.FileExtensions -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Configuration.Ini -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Configuration.Json -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Configuration.KeyPerFile -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Configuration.UserSecrets -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Configuration.Xml -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Configuration -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.DependencyInjection.Abstractions -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.DependencyInjection -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.DiagnosticAdapter -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Diagnostics.HealthChecks.Abstractions -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Diagnostics.HealthChecks -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.FileProviders.Abstractions -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.FileProviders.Composite -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.FileProviders.Embedded -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.FileProviders.Physical -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.FileSystemGlobbing -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.HashCodeCombiner.Sources -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Hosting.Abstractions -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Hosting -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.HostFactoryResolver.Sources -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Http -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Localization.Abstractions -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Localization -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Logging.Abstractions -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Logging.AzureAppServices -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Logging.Configuration -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Logging.Console -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Logging.Debug -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Logging.EventSource -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Logging.EventLog -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Logging.TraceSource -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Logging.Testing -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.ObjectPool -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Options.ConfigurationExtensions -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Options.DataAnnotations -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Options -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.ParameterDefaultValue.Sources -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Primitives -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.TypeNameHelper.Sources -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.ValueStopwatch.Sources -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.WebEncoders -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Internal.Extensions.Refs -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.JSInterop -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Mono.WebAssembly.Interop -> 5.0.0-preview3.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Extensions.Logging -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Internal.AspNetCore.Analyzers -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.AspNetCore.Testing -> 5.0.0-alpha.1.19618.1 (parent: Microsoft.AspNetCore.Razor.Language)
• Microsoft.Net.Compilers.Toolset -> 3.5.0-beta1-19606-04 (parent: Microsoft.Extensions.Logging)

From https://github.com/dotnet/arcade

• Build: 20191208.1
• Date Produced: 12/8/2019 2:06 PM
• Commit: 71ce4c736b882e6112b395a0e92313be5dcb4328
• Branch: refs/heads/master
• Updates:
  • Microsoft.DotNet.Arcade.Sdk -> 5.0.0-beta.19608.1
  • Microsoft.DotNet.GenAPI -> 5.0.0-beta.19608.1
  • Microsoft.DotNet.Helix.Sdk -> 5.0.0-beta.19608.1

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❌ All Checks Successful No un-ignored checks.
• ✔️ No Requested Changes Succeeded - No reviews have requested changes.

[JunTaoLuo]

I'm doubtful of the approach here. Specifically, Extensions.Logging 3.1.0 has a dependency on System.Runtime 4.2.2 which is not found since we are running the 5.0 shared framework. This is a case where we are mixing a 5.0 shared framework and 3.1 packages which is an unsupported scenario. I think we may need to reconsider how we consume EFCore in AspNetCore.

cc @ajcvickers @Pilchie

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❓ Waiting on checks: AspNetCore-ci, AspNetCore-ci (Build Test: Linux Source Build), AspNetCore-ci (Build Test: Ubuntu 16.04 x64), AspNetCore-ci (Build Tests: Helix x64), AspNetCore-ci (Build Test: Templates - Windows Server 2016 x64), AspNetCore-ci (Build Test: macOS 10.13), AspNetCore-ci (Build Test: Windows Server 2016 x64), AspNetCore-ci (Build Build: Linux Musl ARM64), AspNetCore-ci (Build Build: Linux Musl x64), AspNetCore-ci (Build Build: Linux ARM64), AspNetCore-ci (Build Build: Linux x64), AspNetCore-ci (Build Build: Linux ARM), AspNetCore-ci (Build Build: Windows ARM), AspNetCore-ci (Build Build: macOS), AspNetCore-ci (Build Code check), AspNetCore-ci (Build Build: Windows x64/x86)
• ✔️ No Requested Changes Succeeded - No reviews have requested changes.

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❌ All Checks Successful Unsuccessful checks: AspNetCore-ci, AspNetCore-ci (Build Test: Templates - Windows Server 2016 x64), AspNetCore-ci (Build Test: Windows Server 2016 x64)
• ✔️ No Requested Changes Succeeded - No reviews have requested changes.

[wtgodbe]

The build is indeed choosing 4.0.5.0 over 4.0.4.0, presumably because it's higher. Build log shows its used by projects like:

Required by "E:\code\aspnet\aspnetcore\artifacts\bin\MiddlewareAnalysisSample\Debug\netcoreapp5.0\MiddlewareAnalysisSample.dll".

I haven't yet figured out why the 3.1 runtime has a higher assembly version for DiagnosticSource than the 5.0 runtime. This will get fixed automatically once we can ingest a runtime that has the 5.0.0.0 assembly versions (i.e. as soon as the flow is turned on), but until then I'll try to find a workaround.

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❌ All Checks Successful Unsuccessful checks: AspNetCore-ci, AspNetCore-ci (Build Test: Windows Server 2016 x64), AspNetCore-ci (Build Test: Templates - Windows Server 2016 x64)
• ✔️ No Requested Changes Succeeded - No reviews have requested changes.

[wtgodbe]

The projects that try to bring in DiagnosticSource 4.0.5.0 are https://github.com/aspnet/AspNetCore/blob/master/src/Middleware/Diagnostics/test/testassets/DatabaseErrorPageSample/DatabaseErrorPageSample.csproj & https://github.com/aspnet/AspNetCore/blob/master/src/Middleware/Diagnostics.EntityFrameworkCore/src/Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.csproj. Adding References to DiagnosticsSource in those projects removes any mention of 4.0.5.0 from the binlog, but doesn't fix the error.

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❌ All Checks Successful Unsuccessful checks: AspNetCore-ci, AspNetCore-ci (Build Test: Windows Server 2016 x64), AspNetCore-ci (Build Test: Templates - Windows Server 2016 x64)
• ✔️ No Requested Changes Succeeded - No reviews have requested changes.

[JunTaoLuo]

I see issues with System.Runtime.CompilerSErvices.Unsafe:

System.IO.FileLoadException: Could not load file or assembly 'System.Runtime.CompilerServices.Unsafe, Version=4.0.6.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The located assembly's manifest definition does not match the assembly reference. (0x80131040)
File name: 'System.Runtime.CompilerServices.Unsafe, Version=4.0.6.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
 at System.Text.Json.JsonReaderHelper.IndexOfOrLessThan(Byte& searchSpace, Byte value0, Byte value1, Byte lessThan, Int32 length)
 at System.Text.Json.Utf8JsonReader.ConsumeString()
 at System.Text.Json.Utf8JsonReader.ConsumePropertyName()
 at System.Text.Json.Utf8JsonReader.ReadSingleSegment()
 at System.Text.Json.Utf8JsonReader.Read()
 at System.Text.Json.JsonDocument.Parse(ReadOnlySpan1 utf8JsonSpan, Utf8JsonReader reader, MetadataDb& database, StackRowStack& stack)
 at System.Text.Json.JsonDocument.Parse(ReadOnlyMemory1 utf8Json, JsonReaderOptions readerOptions, Byte[] extraRentedBytes)
 at System.Text.Json.JsonDocument.Parse(ReadOnlyMemory1 json, JsonDocumentOptions options)
 at System.Text.Json.JsonDocument.Parse(String json, JsonDocumentOptions options)
 at Microsoft.Extensions.Configuration.Json.JsonConfigurationFileParser.ParseStream(Stream input)
 at Microsoft.Extensions.Configuration.Json.JsonConfigurationProvider.Load(Stream stream)
 at Microsoft.Extensions.Configuration.FileConfigurationProvider.Load(Boolean reload)
 --- End of stack trace from previous location ---
 at Microsoft.Extensions.Configuration.FileConfigurationProvider.HandleException(ExceptionDispatchInfo info)
 at Microsoft.Extensions.Configuration.FileConfigurationProvider.Load(Boolean reload)
 at Microsoft.Extensions.Configuration.FileConfigurationProvider.Load()
 at Microsoft.Extensions.Configuration.ConfigurationRoot..ctor(IList1 providers)
 at Microsoft.Extensions.Configuration.ConfigurationBuilder.Build()
 at Microsoft.Extensions.Hosting.HostBuilder.BuildAppConfiguration()
 at Microsoft.Extensions.Hosting.HostBuilder.Build()
 An error occurred while accessing the Microsoft.Extensions.Hosting services. Continuing without the application service provider. Error: Could not load file or assembly 'System.Runtime.CompilerServices.Unsafe, Version=4.0.6.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The located assembly's manifest definition does not match the assembly reference. (0x80131040)

These might be similar to the DiagnosticSource issues we have seen.

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❓ Waiting on checks: AspNetCore-ci (Build Tests: Helix x64), AspNetCore-ci (Build Test: Templates - Windows Server 2016 x64), AspNetCore-ci (Build Test: Windows Server 2016 x64), AspNetCore-ci (Build Build: Windows ARM), AspNetCore-ci (Build Build: Windows x64/x86), AspNetCore-ci (Build Code check)
• ✔️ No Requested Changes Succeeded - No reviews have requested changes.

[dougbu]

How does this help? This change implies our customers will be unable to build applications mixing EF with our 5.0 release without similar shenanigans -- not a great experience.

[JunTaoLuo]

This is for running dotnet-ef specifically. Not sure what the story for that is going to be @ajcvickers @bricelam ?

[dougbu]

Hmm, why doesn't the tool roll forward on major version?

[bricelam]

dotnet-ef will eventually target netcoreapp5.0

[wtgodbe]

(Copied from email)

I think the DiagnosticSource/CompilerServices.Unsafe thing is a runtime issue – the release/3.0 branch of CoreFx forked off of master, and had all of the same a.b.c.d AssemblyVersions. Then, release/3.1 forked off of release/3.0, and incremented AssemblyVersions to a.b.c+1.d. CoreFx didn’t increment their AssemblyVersions in master until it was too late for us to ingest it, so therefore Microsoft.Netcore.App from master still has the 3.0 era AssemblyVersions, which are lower than the 3.1 ones being consumed by EF. I don’t know if we can fix this without waiting for flow to come out of dotnet/runtime.

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❌ All Checks Successful Unsuccessful checks: AspNetCore-ci (Build Test: Templates - Windows Server 2016 x64), AspNetCore-ci (Build Test: Windows Server 2016 x64)
• ✔️ No Requested Changes Succeeded - No reviews have requested changes.

[wtgodbe]

I've put up #17940 to update everything except EF. I don't think we can ingest EF until we get a dotnet/runtime containing the new 5.0.0.0 AssemblyVersions. Until then, I'm in favor of just disabling the EF->AspNetCore dependency. We can keep this open as it contains some workarounds we might need once we reach that point.

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❌ All Checks Successful Unsuccessful checks: AspNetCore-ci (Build Test: Templates - Windows Server 2016 x64), AspNetCore-ci (Build Test: Windows Server 2016 x64)
• ✔️ No Requested Changes Succeeded - No reviews have requested changes.

[wtgodbe]

If #17940 goes in, I'll push the EF workarounds from this PR to #17947, then close this PR. Until we can ingest dotnet/runtime, I've separated our EFCore ingestion PRs from the rest of our (batched) ingestion PRs.

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❌ All Checks Successful No un-ignored checks.
• ✔️ No Requested Changes Succeeded - No reviews have requested changes.

[Tratcher]

If #17940 goes in, I'll push the EF workarounds from this PR to #17947, then close this PR. Until we can ingest dotnet/runtime, I've separated our EFCore ingestion PRs from the rest of our (batched) ingestion PRs.

@wtgodbe #17940 did go in, should we close this PR now? We'd like a new one with the latest tooling update so we can get roslyn.

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❌ All Checks Successful No un-ignored checks.
• ✔️ No Requested Changes Succeeded - No reviews have requested changes.

[wtgodbe]

@wtgodbe #17940 did go in, should we close this PR now? We'd like a new one with the latest tooling update so we can get roslyn.

I didn't get around to fixing up #17947 yesterday (thanks to the targeting pack shenanigans), I'll do that now & close this

[dotnet-maestro]

Auto-Merge Status

This pull request has not been merged because Maestro++ is waiting on the following merge policies.

• ❌ All Checks Successful No un-ignored checks.
• ✔️ No Requested Changes Succeeded - No reviews have requested changes.