[master] Update dependencies from 4 repositories

[dotnet-maestro]

This pull request updates the following dependencies

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

• Build: 20191024.8
• Date Produced: 10/24/2019 6:09 PM
• Commit: 200bec7b2e7d659077f523a8287f52d99f6f06c0
• Branch: refs/heads/master
• Updates:
  • Microsoft.AspNetCore.Mvc.Razor.Extensions -> 5.0.0-alpha1.19524.8
  • Microsoft.AspNetCore.Razor.Language -> 5.0.0-alpha1.19524.8
  • Microsoft.CodeAnalysis.Razor -> 5.0.0-alpha1.19524.8
  • Microsoft.NET.Sdk.Razor -> 5.0.0-alpha1.19524.8

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.CSharp -> 4.6.0 (parent: Microsoft.NETCore.App.Runtime.win-x64)
• Microsoft.Win32.Registry -> 4.6.0 (parent: Microsoft.NETCore.App.Runtime.win-x64)
• Microsoft.Win32.SystemEvents -> 4.6.0 (parent: Microsoft.NETCore.App.Runtime.win-x64)
• System.ComponentModel.Annotations -> 4.6.0 (parent: Microsoft.NETCore.App.Runtime.win-x64)
• System.Diagnostics.EventLog -> 4.6.0 (parent: Microsoft.NETCore.App.Runtime.win-x64)
• System.Drawing.Common -> 4.6.0 (parent: Microsoft.NETCore.App.Runtime.win-x64)
• System.IO.Pipelines -> 4.6.0 (parent: Microsoft.NETCore.App.Runtime.win-x64)
• System.Net.Http.WinHttpHandler -> 4.6.0 (parent: Microsoft.NETCore.App.Runtime.win-x64)
• System.Net.WebSockets.WebSocketProtocol -> 4.6.0 (parent: Microsoft.NETCore.App.Runtime.win-x64)
• System.Reflection.Metadata -> 1.7.0 (parent: Microsoft.NETCore.App.Runtime.win-x64)
• System.Runtime.CompilerServices.Unsafe -> 4.6.0 (parent: Microsoft.NETCore.App.Runtime.win-x64)
• System.Security.Cryptography.Cng -> 4.6.0 (parent: Microsoft.NETCore.App.Runtime.win-x64)
• System.Security.Cryptography.Pkcs -> 4.6.0 (parent: Microsoft.NETCore.App.Runtime.win-x64)
• System.Security.Cryptography.Xml -> 4.6.0 (parent: Microsoft.NETCore.App.Runtime.win-x64)
• System.Security.Permissions -> 4.6.0 (parent: Microsoft.NETCore.App.Runtime.win-x64)
• System.Security.Principal.Windows -> 4.6.0 (parent: Microsoft.NETCore.App.Runtime.win-x64)
• System.ServiceProcess.ServiceController -> 4.6.0 (parent: Microsoft.NETCore.App.Runtime.win-x64)
• System.Text.Encodings.Web -> 4.6.0 (parent: Microsoft.NETCore.App.Runtime.win-x64)
• System.Text.Json -> 4.6.0 (parent: Microsoft.NETCore.App.Runtime.win-x64)
• System.Threading.Channels -> 4.6.0 (parent: Microsoft.NETCore.App.Runtime.win-x64)
• System.Windows.Extensions -> 4.6.0 (parent: Microsoft.NETCore.App.Runtime.win-x64)
• Microsoft.NETCore.Platforms -> 3.0.0 (parent: Microsoft.NETCore.App.Runtime.win-x64)

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

• Build: 20191029.5
• Date Produced: 10/29/2019 7:39 PM
• Commit: d9886dd9e4545b637ddd7042556c99ef53a37397
• Branch: refs/heads/master
• Updates:
  • Microsoft.EntityFrameworkCore.Tools -> 5.0.0-alpha1.19529.5
  • Microsoft.EntityFrameworkCore.SqlServer -> 5.0.0-alpha1.19529.5
  • dotnet-ef -> 5.0.0-alpha1.19529.5
  • Microsoft.EntityFrameworkCore -> 5.0.0-alpha1.19529.5
  • Microsoft.EntityFrameworkCore.InMemory -> 5.0.0-alpha1.19529.5
  • Microsoft.EntityFrameworkCore.Relational -> 5.0.0-alpha1.19529.5
  • Microsoft.EntityFrameworkCore.Sqlite -> 5.0.0-alpha1.19529.5

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

• Build: 20191027.3
• Date Produced: 10/27/2019 7:01 PM
• Commit: 5ce0aaed2f8df9cd2fe0221a426c021efe37f655
• Branch: refs/heads/master
• Updates:
  • Microsoft.DotNet.Arcade.Sdk -> 5.0.0-beta.19527.3
  • Microsoft.DotNet.GenAPI -> 5.0.0-beta.19527.3
  • Microsoft.DotNet.Helix.Sdk -> 5.0.0-beta.19527.3

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

• Build: 20191028.2
• Date Produced: 10/28/2019 6:25 PM
• Commit: 109766852cdedfd07babca70c56b18a508228e1d
• Branch: refs/heads/master
• Updates:
  • Microsoft.AspNetCore.Blazor.Mono -> 5.0.0-alpha1.19528.2

[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: macOS 10.13), AspNetCore-ci (Build Test: Ubuntu 16.04 x64), AspNetCore-ci (Build Tests: Helix x64), AspNetCore-ci (Build Tests: Helix ARM64), AspNetCore-ci (Build Test: Templates - Windows Server 2016 x64), 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: macOS), AspNetCore-ci (Build Build: Windows ARM), AspNetCore-ci (Build Code check), AspNetCore-ci (Build Build: Windows x64/x86)
• ❌ No Requested Changes There are reviews that have requested changes.

[dougbu]

Is something odd happening in the 5 Dev channel @wtgodbe @mmitche ?

[dougbu]

🆙📅 to pin the Bcl dependency. Have also re-triggered the subscriptions but I'm not sure anything will improve until another EntityFrameworkCore build completes

[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: Linux Source Build), AspNetCore-ci (Build Tests: Helix x64), AspNetCore-ci (Build Test: Windows Server 2016 x64), AspNetCore-ci (Build Code check)
• ❌ No Requested Changes There are reviews that have requested changes.

[dougbu]

Everything moving forward again 😺 though the builds are failing ☹️

[dougbu]

Ugh, now we have three problems here:

1. a breaking change in GenAPI which now writes out a space between parameter attributes and teh parameter type
2. something strange going on within the Arcade SDK:

   /__w/1/s/.packages/microsoft.dotnet.arcade.sdk/5.0.0-beta.19518.2/tools/Tools.proj : error MSB4057: The target "Restore" does not exist in the project.
   

   I'm not sure why this error only fails in the (fake) source build job.
3. multiple test failures, including

   Comments
   { "HelixJobId": "ace56537-9376-4f48-bbc8-ac33b9bc97f6", "HelixWorkItemName": "InMemory.FunctionalTests-netcoreapp5.0" }
   
   Error message
   System.IO.IOException : Authentication failed because the remote party has closed the transport stream.
   
   Stack trace
      at System.Net.Security.SslStream.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
      at System.Net.Security.SslStream.PartialFrameCallback(AsyncProtocolRequest asyncRequest)
   --- End of stack trace from previous location ---
      at System.Net.Security.SslStream.<ThrowIfExceptional>g__ThrowExceptional|141_0(ExceptionDispatchInfo e)
      at System.Net.Security.SslStream.ThrowIfExceptional()
      at System.Net.Security.SslStream.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
      at System.Net.Security.SslStream.EndProcessAuthentication(IAsyncResult result)
      at System.Net.Security.SslStream.EndAuthenticateAsClient(IAsyncResult asyncResult)
      at System.Net.Security.SslStream.<>c.<AuthenticateAsClientAsync>b__65_2(IAsyncResult iar)
      at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
   --- End of stack trace from previous location ---
      at Microsoft.AspNetCore.Server.Kestrel.InMemory.FunctionalTests.HttpsTests.DoesNotThrowObjectDisposedExceptionFromWriteAsyncAfterConnectionIsAborted() in /_/src/Servers/Kestrel/test/InMemory.FunctionalTests/HttpsTests.cs:line 253
      at Microsoft.AspNetCore.Server.Kestrel.InMemory.FunctionalTests.HttpsTests.DoesNotThrowObjectDisposedExceptionFromWriteAsyncAfterConnectionIsAborted() in /_/src/Servers/Kestrel/test/InMemory.FunctionalTests/HttpsTests.cs:line 259
   --- End of stack trace from previous location ---
   

@aspnet/efteam is the InMemory test failure ((3) above) familiar? Has the issue already been addressed in the 'master' branch or 'release/3.1'?

[smitpatel]

@dougbu - While those errors may be coming from InMemory functional tests, based on error it does not seem to be related to EF Core. And we haven't changed anything in InMemory provider either.

[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: Linux Source Build), AspNetCore-ci (Build Tests: Helix x64), AspNetCore-ci (Build Test: Windows Server 2016 x64), AspNetCore-ci (Build Code check)
• ❌ No Requested Changes There are reviews that have requested changes.

[dougbu]

@smitpatel do you know who owns that test area?

[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: Linux Source Build)
• ❌ No Requested Changes There are reviews that have requested changes.

[ryanbrandenburg]

Seems like the mismatched 4.6.0 versions are caused by dotnet/arcade#4155.

[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 Tests: Helix x64), AspNetCore-ci (Build Test: Linux Source Build), AspNetCore-ci (Build Test: macOS 10.13), AspNetCore-ci (Build Test: Ubuntu 16.04 x64), AspNetCore-ci (Build Test: Templates - Windows Server 2016 x64), AspNetCore-ci (Build Test: Windows Server 2016 x64), AspNetCore-ci (Build Build: Linux Musl x64), AspNetCore-ci (Build Build: Linux Musl ARM64), AspNetCore-ci (Build Build: Linux ARM64), AspNetCore-ci (Build Build: Linux ARM), AspNetCore-ci (Build Build: macOS), AspNetCore-ci (Build Build: Linux x64), AspNetCore-ci (Build Build: Windows ARM), AspNetCore-ci (Build Build: Windows x64/x86)
• ❌ No Requested Changes There are reviews that have requested changes.

[mmitche]

Seems like the mismatched 4.6.0 versions are caused by dotnet/arcade#4155.

Yeah, because multiple versions of corefx binaries are appearing in the graph, maestro is choosing the first it finds. There is a work item that @riarenas was working on to try and fix 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 Unsuccessful checks: AspNetCore-ci, AspNetCore-ci (Build Tests: Helix x64), AspNetCore-ci (Build Test: Linux Source Build), AspNetCore-ci (Build Test: macOS 10.13), AspNetCore-ci (Build Test: Ubuntu 16.04 x64), AspNetCore-ci (Build Test: Templates - Windows Server 2016 x64), AspNetCore-ci (Build Test: Windows Server 2016 x64), AspNetCore-ci (Build Build: Linux Musl x64), AspNetCore-ci (Build Build: Linux Musl ARM64), AspNetCore-ci (Build Build: Linux ARM64), AspNetCore-ci (Build Build: Linux ARM), AspNetCore-ci (Build Build: macOS), AspNetCore-ci (Build Build: Linux x64), AspNetCore-ci (Build Build: Windows ARM), AspNetCore-ci (Build Build: Windows x64/x86)
• ❌ No Requested Changes There are reviews that have requested changes.

[mmitche]

@ryanbrandenburg I'm pretty sure dotnet/extensions#2563 will fix 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 Unsuccessful checks: AspNetCore-ci, AspNetCore-ci (Build Test: Linux Source Build), AspNetCore-ci (Build Test: macOS 10.13), AspNetCore-ci (Build Test: Ubuntu 16.04 x64), AspNetCore-ci (Build Test: Templates - Windows Server 2016 x64), AspNetCore-ci (Build Tests: Helix x64), AspNetCore-ci (Build Build: Linux Musl x64), AspNetCore-ci (Build Test: Windows Server 2016 x64), AspNetCore-ci (Build Build: Linux Musl ARM64), AspNetCore-ci (Build Build: Linux x64), AspNetCore-ci (Build Build: Linux ARM64), AspNetCore-ci (Build Build: Linux ARM), AspNetCore-ci (Build Build: macOS), AspNetCore-ci (Build Build: Windows ARM), AspNetCore-ci (Build Build: Windows x64/x86), AspNetCore-ci (Build Code check)
• ❌ No Requested Changes There are reviews that have requested changes.

[halter73]

I'm guessing @mikaelm12 doesn't want to be re-added as a code owner.

Suggested change

	/src/SignalR/ @mikaelm12 @BrennanConroy @halter73 @anurse
	/src/SignalR/ @BrennanConroy @halter73 @anurse

[halter73]

Make sure you don't undo #15156 when you merge this. I'm not sure if there is ore stuff like this, but this seemed suspicious. @javiercn

It seems like 6dab6fb is bad.

[BrennanConroy]

We need to fix this up

[BrennanConroy]

@dougbu You said you fixed it but it's still 4.6.0??

[BrennanConroy]

What happened...