The layout view '...' could not be located

Describe the bug
I've upgraded a complex .NET Core 2.2 solution to .NET Core 3.0 over the weekend, and I am now running into somewhat random, but completely inexplicable issues when debugging the ASP.NET Core projects.
The complexity of the solution is that there are five "main" ASP.NET Core projects, and one "shared" ASP.NET Core project. The shared project is set as a class library output. It is an ASP.NET Core project so I can work with TypeScript properly, and for base views. I attempted to make a Razor Class Library before but I couldn't get it work, gave up and moved on with my life.
The shared project has some views in a Features folder, in this case _Layout.cshtml. This view is used by two other main projects.
When I attempt to run the projects from Visual Studio, F5 or CTRL+F5, I am always greeted by this exception:

InvalidOperationException: The layout view '~/Features/_Layout.cshtml' could not be located. The following locations were searched: ~/Features/_Layout.cshtml

The only thing I've found to make the exception go away is to edit the project's file and either comment or un-comment the <AddRazorMvcSupport>true</AddRazorMvcSupport> property and re-run. Making changes, rebuilding, and debugging after that works fine.
To be honest, I'm not sure if that is a real property, I saw it either in GitHub issue discussion or a SO thread and copied it over and I can't find the link to it anymore. It was part of the Razor SDK. For all I know, commenting or un-commenting anything at random in the project file will fix the issue, I just haven't tested it.
This does not appear to be an issue when the project is published in release mode to IIS. This only appears to be an issue when debugging through Visual Studio.
I cannot manually test using the CLI because I use named URLs for debugging which are required for the app's functionality, and manually running the apps gives it localhost as the URL.
Looking through the output folder, the shared project's .View.dll file is there as expected.
To Reproduce

Using Windows 10, 1903 (forced me into an upgrade on Friday, was 1803 before that)
Using ASP.NET Core 3.0
Using Visual Studio 16.3.1
Create two ASP.NET Core projects.

Set one to output as a class library, this is the "shared" project now.
Add a _Layout.cshtml file to the shared project.
Add a view to the other "main" project that references the layout from the shared project.

To be honest, I'm not sure if this will reproduce the error. My projects do a lot of other things such as authentication and authorization, etc., that are almost impossible to describe here without writing a book and exposing, potentially, private business logic.
The production server is Windows Server 2019, 1809 on AWS.
The bottom line is that this issue occurred as a result of either upgrading to Visual Studio 16.3 or .NET Core 3.0. This never occurred while I was on Visual Studio 16.2 and .NET Core 2.2.
Expected behavior
I expect the view in the shared project to be found and used, always.
Additional context
Here is the stack trace:
Microsoft.AspNetCore.Mvc.Razor.RazorView.GetLayoutPage(ViewContext context, string executingFilePath, string layoutPath)
Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderLayoutAsync(ViewContext context, ViewBufferTextWriter bodyWriter)
Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderAsync(ViewContext context)
Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.ExecuteAsync(ViewContext viewContext, string contentType, Nullable<int> statusCode)
Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.ExecuteAsync(ActionContext actionContext, IView view, ViewDataDictionary viewData, ITempDataDictionary tempData, string contentType, Nullable<int> statusCode)
Microsoft.AspNetCore.Mvc.ViewFeatures.ViewResultExecutor.ExecuteAsync(ActionContext context, ViewResult result)
Microsoft.AspNetCore.Mvc.ViewResult.ExecuteResultAsync(ActionContext context)
Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResultFilterAsync>g__Awaited|29_0<TFilter, TFilterAsync>(ResourceInvoker invoker, Task lastTask, State next, Scope scope, object state, bool isCompleted)
Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResultExecutedContextSealed context)
Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.ResultNext<TFilter, TFilterAsync>(ref State next, ref Scope scope, ref object state, ref bool isCompleted)
Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeResultFilters()
Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResourceFilter>g__Awaited|24_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, object state, bool isCompleted)
Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context)
Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(ref State next, ref Scope scope, ref object state, ref bool isCompleted)
Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeFilterPipelineAsync()
Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Logged|17_1(ResourceInvoker invoker)
Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
REDACTED.Web.ApplicationUserMiddleware.InvokeAsync(HttpContext context, IApplicationUserServices services) in ApplicationUserMiddleware.cs
+
			await Next(context);
Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
Arex388.AspNetCore.HtmlMinifierMiddleware.InvokeAsync(HttpContext context)
Microsoft.AspNetCore.Builder.Extensions.MapMiddleware.Invoke(HttpContext context)
StackExchange.Profiling.MiniProfilerMiddleware.Invoke(HttpContext context) in MiniProfilerMiddleware.cs
Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.MigrationsEndPointMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.DatabaseErrorPageMiddleware.Invoke(HttpContext httpContext)
Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.DatabaseErrorPageMiddleware.Invoke(HttpContext httpContext)
Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

After posting this I remembered that I thankfully made a copy of the solution before doing the upgrade to .NET Core 3.0. I restored the copy and ran it several times by closing IIS Express and CTRL+F5-ing. Each run was successful and no exception was thrown.
This rules out Visual Studio as being the culprit and points to .NET Core 3.0 exclusively, as far as I can interpret the test result.

I've also confirmed that any random change to the project file triggers the "fix". I just tried adding an empty PropertyGroup and it was enough to stop the exception.

@arex388 I tried an app based on your steps - https://github.com/pranavkm/repro/tree/14574 - and I can't reproduce the view lookup failing. Could you try playing around with it to see if it's problematic for you?
One thing that might help would be turn on the logging in your application to Debug and it might provide hints as to what's causing the lookup to fail.

@pranavkm, I added the debug logging and captured this:
Microsoft.AspNetCore.Hosting.Diagnostics: Information: Request starting HTTP/1.1 GET http://REDACTED/
Microsoft.AspNetCore.Authorization.DefaultAuthorizationService: Information: Authorization was successful.
 Executing controller action with signature System.Threading.Tasks.Task`1[Microsoft.AspNetCore.Mvc.IActionResult] Dashboard() on controller REDACTED.
Microsoft.AspNetCore.Mvc.ViewFeatures.ViewResultExecutor: Information: Executing ViewResult, running view Dashboard.
Exception thrown: 'System.InvalidOperationException' in Microsoft.AspNetCore.Mvc.Razor.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker: Information: Executed action REDACTED in<PHONE_NUMBER>0000004ms
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Microsoft.AspNetCore.Routing.EndpointMiddleware: Information: Executed endpoint 'REDACTED'
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in Arex388.AspNetCore.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware: Error: An unhandled exception has occurred while executing the request.

System.InvalidOperationException: The layout view '~/Features/_Layout.cshtml' could not be located. The following locations were searched:
~/Features/_Layout.cshtml
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.GetLayoutPage(ViewContext context, String executingFilePath, String layoutPath)
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderLayoutAsync(ViewContext context, ViewBufferTextWriter bodyWriter)
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderAsync(ViewContext context)
   at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.ExecuteAsync(ViewContext viewContext, String contentType, Nullable`1 statusCode)
   at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.ExecuteAsync(ActionContext actionContext, IView view, ViewDataDictionary viewData, ITempDataDictionary tempData, String contentType, Nullable`1 statusCode)
   at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewResultExecutor.ExecuteAsync(ActionContext context, ViewResult result)
   at Microsoft.AspNetCore.Mvc.ViewResult.ExecuteResultAsync(ActionContext context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResultFilterAsync>g__Awaited|29_0[TFilter,TFilterAsync](ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResultExecutedContextSealed context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.ResultNext[TFilter,TFilterAsync](State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeResultFilters()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResourceFilter>g__Awaited|24_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeFilterPipelineAsync()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Logged|17_1(ResourceInvoker invoker)
   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
   at REDACTED.Web.ApplicationUserMiddleware.InvokeAsync(HttpContext context, IApplicationUserServices services) in REDACTED:line 52
   at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
   at Arex388.AspNetCore.HtmlMinifierMiddleware.InvokeAsync(HttpContext context)
   at Microsoft.AspNetCore.Builder.Extensions.MapMiddleware.Invoke(HttpContext context)
   at StackExchange.Profiling.MiniProfilerMiddleware.Invoke(HttpContext context) in C:\projects\dotnet\src\MiniProfiler.AspNetCore\MiniProfilerMiddleware.cs:line 107
   at Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.MigrationsEndPointMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.DatabaseErrorPageMiddleware.Invoke(HttpContext httpContext)
   at Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.DatabaseErrorPageMiddleware.Invoke(HttpContext httpContext)
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.Hosting.Diagnostics: Information: Request finished in 912.1462ms 500 text/html; charset=utf-8

I thought it had something to do with a NuGet package I've made, Arex388.AspNetCore, because it was targeting .NET Core 2.2 and maybe that was creating conflicts. This morning I upgraded it to .NET Core 3.0, targeting the Web SDK, and updated the solution. Unfortunately, it hasn't helped.
I see a bunch of exceptions being thrown in System.Private.CoreLib.dll, but haven't a clue how to find out why they're being thrown. Do you have any recommendations? Thanks!

@arex388 these look like Information logs. Could you change the log level for everything in config to Debug? See https://docs.microsoft.com/en-us/aspnet/core/fundamentals/logging/?view=aspnetcore-3.0#log-filtering

@pranavkm I changed the log level for all to Debug:
"Logging": {
	"LogLevel": {
		"Default": "Debug"
	}
}

Is this correct for what you wanted? This is what I captured. It doesn't look anymore revealing to me though:
Microsoft.AspNetCore.Hosting.Diagnostics: Information: Request starting HTTP/1.1 GET http://admin.REDACTED.local/
Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware: Debug: The request path / does not match a supported file type
Microsoft.AspNetCore.Routing.Matching.DfaMatcher: Debug: 2 candidate(s) found for the request path '/'
Microsoft.AspNetCore.Routing.Matching.DfaMatcher: Debug: Endpoint 'REDACTED.Web.Admin.Features.Default.DefaultController.Dashboard (REDACTED.Web.Admin)' with route pattern '' is valid for the request path '/'
Microsoft.AspNetCore.Routing.Matching.DfaMatcher: Debug: Endpoint 'REDACTED.Web.Admin.Features.Default.DefaultController.Gone (REDACTED.Web.Admin)' with route pattern '{*url}' is valid for the request path '/'
Microsoft.AspNetCore.Routing.EndpointRoutingMiddleware: Debug: Request matched endpoint 'REDACTED.Web.Admin.Features.Default.DefaultController.Dashboard (REDACTED.Web.Admin)'
Microsoft.AspNetCore.Authentication.Cookies.CookieAuthenticationHandler: Debug: AuthenticationScheme: Identity.Application was successfully authenticated.
Microsoft.AspNetCore.Authorization.DefaultAuthorizationService: Information: Authorization was successful.
Microsoft.EntityFrameworkCore.Database.Command: Debug: Creating DbCommand for 'ExecuteReader'.
Microsoft.EntityFrameworkCore.Database.Command: Debug: Created DbCommand for 'ExecuteReader' (1ms).
Microsoft.EntityFrameworkCore.Database.Connection: Debug: Opening connection to database 'REDACTED' on server 'REDACTED'.
Microsoft.EntityFrameworkCore.Database.Connection: Debug: Opened connection to database 'REDACTED' on server 'REDACTED'.

Microsoft.EntityFrameworkCore.Database.Connection: Debug: Closing connection to database 'REDACTED' on server 'REDACTED'.
Microsoft.EntityFrameworkCore.Database.Connection: Debug: Closed connection to database 'REDACTED' on server 'REDACTED'.
Microsoft.AspNetCore.Routing.EndpointMiddleware: Information: Executing endpoint 'REDACTED.Web.Admin.Features.Default.DefaultController.Dashboard (REDACTED.Web.Admin)'
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker: Information: Route matched with {action = "Dashboard", controller = "Default"}. Executing controller action with signature System.Threading.Tasks.Task`1[Microsoft.AspNetCore.Mvc.IActionResult] Dashboard() on controller REDACTED.Web.Admin.Features.Default.DefaultController (REDACTED.Web.Admin).
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker: Debug: Execution plan of authorization filters (in the following order): None
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker: Debug: Execution plan of resource filters (in the following order): Microsoft.AspNetCore.Mvc.ViewFeatures.Filters.SaveTempDataFilter
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker: Debug: Execution plan of action filters (in the following order): Microsoft.AspNetCore.Mvc.Filters.ControllerActionFilter (Order: -2147483648), Microsoft.AspNetCore.Mvc.ModelBinding.UnsupportedContentTypeFilter (Order: -3000), StackExchange.Profiling.Internal.ProfilingActionFilter (Order: 0)
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker: Debug: Execution plan of exception filters (in the following order): None
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker: Debug: Execution plan of result filters (in the following order): Microsoft.AspNetCore.Mvc.ViewFeatures.Filters.SaveTempDataFilter, StackExchange.Profiling.Internal.ProfilingActionFilter (Order: 0)
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker: Debug: Executing controller factory for controller REDACTED.Web.Admin.Features.Default.DefaultController (REDACTED.Web.Admin)
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker: Debug: Executed controller factory for controller REDACTED.Web.Admin.Features.Default.DefaultController (REDACTED.Web.Admin)
Microsoft.AspNetCore.Mvc.Razor.RazorViewEngine: Debug: View lookup cache hit for view 'Dashboard' in controller 'Default'.
Microsoft.AspNetCore.Mvc.ViewFeatures.ViewResultExecutor: Information: Executing ViewResult, running view Dashboard.
Microsoft.AspNetCore.Mvc.ViewFeatures.ViewResultExecutor: Debug: The view path '/Features/Default/Dashboard.cshtml' was found in 1.6172ms.
Exception thrown: 'System.InvalidOperationException' in Microsoft.AspNetCore.Mvc.Razor.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker: Information: Executed action REDACTED.Web.Admin.Features.Default.DefaultController.Dashboard (REDACTED.Web.Admin) in 301.954ms
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Microsoft.AspNetCore.Routing.EndpointMiddleware: Information: Executed endpoint 'REDACTED.Web.Admin.Features.Default.DefaultController.Dashboard (REDACTED.Web.Admin)'
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in Arex388.AspNetCore.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.DatabaseErrorPageMiddleware: Debug: System.InvalidOperationException occurred, checking if Entity Framework recorded this exception as resulting from a failed database operation.
Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.DatabaseErrorPageMiddleware: Debug: Entity Framework did not record any exceptions due to failed database operations. This means the current exception is not a failed Entity Framework database operation, or the current exception occurred from a DbContext that was not obtained from request services.
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Exception thrown: 'System.InvalidOperationException' in System.Private.CoreLib.dll
Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware: Error: An unhandled exception has occurred while executing the request.

System.InvalidOperationException: The layout view '~/Features/_Layout.cshtml' could not be located. The following locations were searched:
~/Features/_Layout.cshtml
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.GetLayoutPage(ViewContext context, String executingFilePath, String layoutPath)
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderLayoutAsync(ViewContext context, ViewBufferTextWriter bodyWriter)
   at Microsoft.AspNetCore.Mvc.Razor.RazorView.RenderAsync(ViewContext context)
   at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.ExecuteAsync(ViewContext viewContext, String contentType, Nullable`1 statusCode)
   at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.ExecuteAsync(ActionContext actionContext, IView view, ViewDataDictionary viewData, ITempDataDictionary tempData, String contentType, Nullable`1 statusCode)
   at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewResultExecutor.ExecuteAsync(ActionContext context, ViewResult result)
   at Microsoft.AspNetCore.Mvc.ViewResult.ExecuteResultAsync(ActionContext context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResultFilterAsync>g__Awaited|29_0[TFilter,TFilterAsync](ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResultExecutedContextSealed context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.ResultNext[TFilter,TFilterAsync](State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeResultFilters()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResourceFilter>g__Awaited|24_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeFilterPipelineAsync()
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Logged|17_1(ResourceInvoker invoker)
   at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
   at REDACTED.Web.ApplicationUserMiddleware.InvokeAsync(HttpContext context, IApplicationUserServices services) in E:\Visual Studio\REDACTED\REDACTED.Web\Middlewares\ApplicationUserMiddleware.cs:line 52
   at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
   at Arex388.AspNetCore.HtmlMinifierMiddleware.InvokeAsync(HttpContext context)
   at Arex388.AspNetCore.AntiFaviconMiddleware.InvokeAsync(HttpContext context)
   at Microsoft.AspNetCore.Builder.Extensions.MapMiddleware.Invoke(HttpContext context)
   at StackExchange.Profiling.MiniProfilerMiddleware.Invoke(HttpContext context) in C:\projects\dotnet\src\MiniProfiler.AspNetCore\MiniProfilerMiddleware.cs:line 107
   at Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.MigrationsEndPointMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.DatabaseErrorPageMiddleware.Invoke(HttpContext httpContext)
   at Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.DatabaseErrorPageMiddleware.Invoke(HttpContext httpContext)
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.Hosting.Diagnostics: Information: Request finished in 874.8821ms 500 text/html; charset=utf-8

And here's the successful result after editing the project file:
Microsoft.AspNetCore.Hosting.Diagnostics: Information: Request starting HTTP/1.1 GET http://admin.REDACTED.local/
Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware: Debug: The request path / does not match a supported file type
Microsoft.AspNetCore.Routing.Matching.DfaMatcher: Debug: 2 candidate(s) found for the request path '/'
Microsoft.AspNetCore.Routing.Matching.DfaMatcher: Debug: Endpoint 'REDACTED.Web.Admin.Features.Default.DefaultController.Dashboard (REDACTED.Web.Admin)' with route pattern '' is valid for the request path '/'
Microsoft.AspNetCore.Routing.Matching.DfaMatcher: Debug: Endpoint 'REDACTED.Web.Admin.Features.Default.DefaultController.Gone (REDACTED.Web.Admin)' with route pattern '{*url}' is valid for the request path '/'
Microsoft.AspNetCore.Routing.EndpointRoutingMiddleware: Debug: Request matched endpoint 'REDACTED.Web.Admin.Features.Default.DefaultController.Dashboard (REDACTED.Web.Admin)'
Microsoft.AspNetCore.Authentication.Cookies.CookieAuthenticationHandler: Debug: AuthenticationScheme: Identity.Application was successfully authenticated.
Microsoft.AspNetCore.Authorization.DefaultAuthorizationService: Information: Authorization was successful.
Microsoft.EntityFrameworkCore.Database.Command: Debug: Creating DbCommand for 'ExecuteReader'.
Microsoft.EntityFrameworkCore.Database.Command: Debug: Created DbCommand for 'ExecuteReader' (0ms).
Microsoft.EntityFrameworkCore.Database.Connection: Debug: Opening connection to database 'REDACTED' on server 'REDACTED'.
Microsoft.EntityFrameworkCore.Database.Connection: Debug: Opened connection to database 'REDACTED' on server 'REDACTED'.

Microsoft.EntityFrameworkCore.Database.Connection: Debug: Closing connection to database 'REDACTED' on server 'REDACTED'.
Microsoft.EntityFrameworkCore.Database.Connection: Debug: Closed connection to database 'REDACTED' on server 'REDACTED'.
Microsoft.AspNetCore.Routing.EndpointMiddleware: Information: Executing endpoint 'REDACTED.Web.Admin.Features.Default.DefaultController.Dashboard (REDACTED.Web.Admin)'
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker: Information: Route matched with {action = "Dashboard", controller = "Default"}. Executing controller action with signature System.Threading.Tasks.Task`1[Microsoft.AspNetCore.Mvc.IActionResult] Dashboard() on controller REDACTED.Web.Admin.Features.Default.DefaultController (REDACTED.Web.Admin).
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker: Debug: Execution plan of authorization filters (in the following order): None
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker: Debug: Execution plan of resource filters (in the following order): Microsoft.AspNetCore.Mvc.ViewFeatures.Filters.SaveTempDataFilter
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker: Debug: Execution plan of action filters (in the following order): Microsoft.AspNetCore.Mvc.Filters.ControllerActionFilter (Order: -2147483648), Microsoft.AspNetCore.Mvc.ModelBinding.UnsupportedContentTypeFilter (Order: -3000), StackExchange.Profiling.Internal.ProfilingActionFilter (Order: 0)
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker: Debug: Execution plan of exception filters (in the following order): None
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker: Debug: Execution plan of result filters (in the following order): Microsoft.AspNetCore.Mvc.ViewFeatures.Filters.SaveTempDataFilter, StackExchange.Profiling.Internal.ProfilingActionFilter (Order: 0)
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker: Debug: Executing controller factory for controller REDACTED.Web.Admin.Features.Default.DefaultController (REDACTED.Web.Admin)
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker: Debug: Executed controller factory for controller REDACTED.Web.Admin.Features.Default.DefaultController (REDACTED.Web.Admin)
Microsoft.AspNetCore.Mvc.Razor.RazorViewEngine: Debug: View lookup cache hit for view 'Dashboard' in controller 'Default'.
Microsoft.AspNetCore.Mvc.ViewFeatures.ViewResultExecutor: Information: Executing ViewResult, running view Dashboard.
Microsoft.AspNetCore.Mvc.ViewFeatures.ViewResultExecutor: Debug: The view path '/Features/Default/Dashboard.cshtml' was found in 1.6991ms.
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Found the endpoints REDACTED.Web.Admin.Features.Default.DefaultController.Dashboard (REDACTED.Web.Admin), Route: iot-console/{action:slugify=Default}, Route: {controller:slugify}/{id:int}/{action:slugify=Edit}, Route: {controller:slugify}/{action:slugify=Default} for address Microsoft.AspNetCore.Routing.RouteValuesAddress
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Successfully processed template  for REDACTED.Web.Admin.Features.Default.DefaultController.Dashboard (REDACTED.Web.Admin) resulting in  and
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Link generation succeeded for endpoints REDACTED.Web.Admin.Features.Default.DefaultController.Dashboard (REDACTED.Web.Admin), Route: iot-console/{action:slugify=Default}, Route: {controller:slugify}/{id:int}/{action:slugify=Edit}, Route: {controller:slugify}/{action:slugify=Default} with result /
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Found the endpoints Route: iot-console/{action:slugify=Default}, Route: {controller:slugify}/{id:int}/{action:slugify=Edit}, Route: {controller:slugify}/{action:slugify=Default} for address Microsoft.AspNetCore.Routing.RouteValuesAddress
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Failed to process the template iot-console/{action:slugify=Default} for Route: iot-console/{action:slugify=Default}. A required route value is missing, or has a different value from the required default values. Supplied ambient values { "action": "Dashboard", "controller": "Default" } and { "action": "Default", "controller": "Devices" } with default values { "action": "Default", "controller": "IoTConsole" }
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Failed to process the template {controller:slugify}/{id:int}/{action:slugify=Edit} for Route: {controller:slugify}/{id:int}/{action:slugify=Edit}. A required route value is missing, or has a different value from the required default values. Supplied ambient values { "action": "Dashboard", "controller": "Default" } and { "action": "Default", "controller": "Devices" } with default values { "action": "Edit" }
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Successfully processed template {controller:slugify}/{action:slugify=Default} for Route: {controller:slugify}/{action:slugify=Default} resulting in /devices and
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Link generation succeeded for endpoints Route: iot-console/{action:slugify=Default}, Route: {controller:slugify}/{id:int}/{action:slugify=Edit}, Route: {controller:slugify}/{action:slugify=Default} with result /devices
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Found the endpoints Route: iot-console/{action:slugify=Default}, Route: {controller:slugify}/{id:int}/{action:slugify=Edit}, Route: {controller:slugify}/{action:slugify=Default} for address Microsoft.AspNetCore.Routing.RouteValuesAddress
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Failed to process the template iot-console/{action:slugify=Default} for Route: iot-console/{action:slugify=Default}. A required route value is missing, or has a different value from the required default values. Supplied ambient values { "action": "Dashboard", "controller": "Default" } and { "action": "Default", "controller": "Accounts" } with default values { "action": "Default", "controller": "IoTConsole" }
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Failed to process the template {controller:slugify}/{id:int}/{action:slugify=Edit} for Route: {controller:slugify}/{id:int}/{action:slugify=Edit}. A required route value is missing, or has a different value from the required default values. Supplied ambient values { "action": "Dashboard", "controller": "Default" } and { "action": "Default", "controller": "Accounts" } with default values { "action": "Edit" }
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Successfully processed template {controller:slugify}/{action:slugify=Default} for Route: {controller:slugify}/{action:slugify=Default} resulting in /accounts and
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Link generation succeeded for endpoints Route: iot-console/{action:slugify=Default}, Route: {controller:slugify}/{id:int}/{action:slugify=Edit}, Route: {controller:slugify}/{action:slugify=Default} with result /accounts
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Found the endpoints Route: iot-console/{action:slugify=Default}, Route: {controller:slugify}/{id:int}/{action:slugify=Edit}, Route: {controller:slugify}/{action:slugify=Default} for address Microsoft.AspNetCore.Routing.RouteValuesAddress
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Failed to process the template iot-console/{action:slugify=Default} for Route: iot-console/{action:slugify=Default}. A required route value is missing, or has a different value from the required default values. Supplied ambient values { "action": "Dashboard", "controller": "Default" } and { "action": "Default", "controller": "Users" } with default values { "action": "Default", "controller": "IoTConsole" }
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Failed to process the template {controller:slugify}/{id:int}/{action:slugify=Edit} for Route: {controller:slugify}/{id:int}/{action:slugify=Edit}. A required route value is missing, or has a different value from the required default values. Supplied ambient values { "action": "Dashboard", "controller": "Default" } and { "action": "Default", "controller": "Users" } with default values { "action": "Edit" }
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Successfully processed template {controller:slugify}/{action:slugify=Default} for Route: {controller:slugify}/{action:slugify=Default} resulting in /users and
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Link generation succeeded for endpoints Route: iot-console/{action:slugify=Default}, Route: {controller:slugify}/{id:int}/{action:slugify=Edit}, Route: {controller:slugify}/{action:slugify=Default} with result /users
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Found the endpoints Route: iot-console/{action:slugify=Default}, Route: {controller:slugify}/{id:int}/{action:slugify=Edit}, Route: {controller:slugify}/{action:slugify=Default} for address Microsoft.AspNetCore.Routing.RouteValuesAddress
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Failed to process the template iot-console/{action:slugify=Default} for Route: iot-console/{action:slugify=Default}. A required route value is missing, or has a different value from the required default values. Supplied ambient values { "action": "Dashboard", "controller": "Default" } and { "action": "Default", "controller": "Reports" } with default values { "action": "Default", "controller": "IoTConsole" }
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Failed to process the template {controller:slugify}/{id:int}/{action:slugify=Edit} for Route: {controller:slugify}/{id:int}/{action:slugify=Edit}. A required route value is missing, or has a different value from the required default values. Supplied ambient values { "action": "Dashboard", "controller": "Default" } and { "action": "Default", "controller": "Reports" } with default values { "action": "Edit" }
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Successfully processed template {controller:slugify}/{action:slugify=Default} for Route: {controller:slugify}/{action:slugify=Default} resulting in /reports and
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Link generation succeeded for endpoints Route: iot-console/{action:slugify=Default}, Route: {controller:slugify}/{id:int}/{action:slugify=Edit}, Route: {controller:slugify}/{action:slugify=Default} with result /reports
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Found the endpoints Route: iot-console/{action:slugify=Default}, Route: {controller:slugify}/{id:int}/{action:slugify=Edit}, Route: {controller:slugify}/{action:slugify=Default} for address Microsoft.AspNetCore.Routing.RouteValuesAddress
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Failed to process the template iot-console/{action:slugify=Default} for Route: iot-console/{action:slugify=Default}. A required route value is missing, or has a different value from the required default values. Supplied ambient values { "action": "Dashboard", "controller": "Default" } and { "action": "Default", "controller": "Search" } with default values { "action": "Default", "controller": "IoTConsole" }
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Failed to process the template {controller:slugify}/{id:int}/{action:slugify=Edit} for Route: {controller:slugify}/{id:int}/{action:slugify=Edit}. A required route value is missing, or has a different value from the required default values. Supplied ambient values { "action": "Dashboard", "controller": "Default" } and { "action": "Default", "controller": "Search" } with default values { "action": "Edit" }
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Successfully processed template {controller:slugify}/{action:slugify=Default} for Route: {controller:slugify}/{action:slugify=Default} resulting in /search and
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Link generation succeeded for endpoints Route: iot-console/{action:slugify=Default}, Route: {controller:slugify}/{id:int}/{action:slugify=Edit}, Route: {controller:slugify}/{action:slugify=Default} with result /search
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Found the endpoints Route: iot-console/{action:slugify=Default}, Route: {controller:slugify}/{id:int}/{action:slugify=Edit}, Route: {controller:slugify}/{action:slugify=Default} for address Microsoft.AspNetCore.Routing.RouteValuesAddress
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Failed to process the template iot-console/{action:slugify=Default} for Route: iot-console/{action:slugify=Default}. A required route value is missing, or has a different value from the required default values. Supplied ambient values { "action": "Dashboard", "controller": "Default" } and { "action": "Default", "controller": "Settings" } with default values { "action": "Default", "controller": "IoTConsole" }
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Failed to process the template {controller:slugify}/{id:int}/{action:slugify=Edit} for Route: {controller:slugify}/{id:int}/{action:slugify=Edit}. A required route value is missing, or has a different value from the required default values. Supplied ambient values { "action": "Dashboard", "controller": "Default" } and { "action": "Default", "controller": "Settings" } with default values { "action": "Edit" }
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Successfully processed template {controller:slugify}/{action:slugify=Default} for Route: {controller:slugify}/{action:slugify=Default} resulting in /settings and
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Link generation succeeded for endpoints Route: iot-console/{action:slugify=Default}, Route: {controller:slugify}/{id:int}/{action:slugify=Edit}, Route: {controller:slugify}/{action:slugify=Default} with result /settings
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Found the endpoints REDACTED.Web.Admin.Features.Default.DefaultController.SignOut (REDACTED.Web.Admin), Route: iot-console/{action:slugify=Default}, Route: {controller:slugify}/{id:int}/{action:slugify=Edit}, Route: {controller:slugify}/{action:slugify=Default} for address Microsoft.AspNetCore.Routing.RouteValuesAddress
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Successfully processed template sign-out for REDACTED.Web.Admin.Features.Default.DefaultController.SignOut (REDACTED.Web.Admin) resulting in /sign-out and
Microsoft.AspNetCore.Routing.DefaultLinkGenerator: Debug: Link generation succeeded for endpoints REDACTED.Web.Admin.Features.Default.DefaultController.SignOut (REDACTED.Web.Admin), Route: iot-console/{action:slugify=Default}, Route: {controller:slugify}/{id:int}/{action:slugify=Edit}, Route: {controller:slugify}/{action:slugify=Default} with result /sign-out
Microsoft.AspNetCore.Mvc.ViewFeatures.ViewResultExecutor: Information: Executed ViewResult - view Dashboard executed in 32.7506ms.
Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker: Information: Executed action REDACTED.Web.Admin.Features.Default.DefaultController.Dashboard (REDACTED.Web.Admin) in 36.129400000000004ms
Microsoft.AspNetCore.Routing.EndpointMiddleware: Information: Executed endpoint 'REDACTED.Web.Admin.Features.Default.DefaultController.Dashboard (REDACTED.Web.Admin)'
Microsoft.AspNetCore.Hosting.Diagnostics: Information: Request finished in 136.6117ms 200 text/html; charset=utf-8
Microsoft.AspNetCore.Hosting.Diagnostics: Information: Request starting HTTP/1.1 GET http://admin.REDACTED.local/styles.min.css?v=3pN9pDIy-rDvQq99S7lpEC_9uJvPG0iGtf7m-Ft4WGI
Microsoft.AspNetCore.Hosting.Diagnostics: Information: Request starting HTTP/1.1 GET http://admin.REDACTED.local/scripts.min.js?v=CsQXqQ0o4ZA9DrPF5z7kHSSNdbrKGybNnvT2XgKdP94
Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware: Information: The file /scripts.min.js was not modified
Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware: Information: The file /styles.min.css was not modified
Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware: Debug: Handled. Status code: 304 File: /scripts.min.js
Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware: Debug: Handled. Status code: 304 File: /styles.min.css
Microsoft.AspNetCore.Hosting.Diagnostics: Information: Request finished in 8.3436ms 304 text/css
Microsoft.AspNetCore.Hosting.Diagnostics: Information: Request finished in 6.4619ms 304 application/javascript
Microsoft.AspNetCore.Hosting.Diagnostics: Information: Request starting HTTP/1.1 POST http://admin.REDACTED.local/mini-profiler-resources/results application/json 45
Microsoft.AspNetCore.Hosting.Diagnostics: Information: Request starting HTTP/1.1 POST http://admin.REDACTED.local/mini-profiler-resources/results application/json 45
Microsoft.AspNetCore.Hosting.Diagnostics: Information: Request starting HTTP/1.1 POST http://admin.REDACTED.local/mini-profiler-resources/results application/json 798
Microsoft.AspNetCore.Hosting.Diagnostics: Information: Request finished in 3.0225ms 200 application/json
Microsoft.AspNetCore.Hosting.Diagnostics: Information: Request finished in 3.0225ms 200 application/json
Microsoft.AspNetCore.Hosting.Diagnostics: Information: Request finished in 6.151800000000001ms 200 application/json

The exceptions in System.Private.CoreLib.dll are gone and the view is loaded as expected.

Yeah, I guess the logging doesn't really help figuring out why it couldn't be found. Could you walk me through what triggers the failure? I listed a sample app earlier, were you able to reproduce the problem using it?

I ran the sample app, but it didn't reproduce the error. There are drastic differences between the sample app and my apps, starting with the file structure. I'm following the Vertical Slices structure with Features folders. And it just gets more complex from there with AWS Systems Manager to load keys, and connection strings, extensions to build up the IServiceCollection and IApplicationBuilder, so on and so forth.
The exception consistently occurs when I open Visual Studio, load the solution, and run the project.  If I close and re-open Visual Studio, the process repeats. Sometimes if I have Visual Studio open for a long time after I've forced the exception to go away, it will throw again, and then I have to do the project edit dance.
Again, running my back up of the solution while it was still in .NET Core 2.2 with the same version of Visual Studio, there are not problems. This only occurred after upgrading to .NET Core 3.0. It may not even be a .NET Core 3.0 issue, but and issue with the config files for the solution? I had to go into them and manually remove artifacts that were just left over from before to fix other issues during the upgrade.
I don't know how feasible this is, but would it be possible for you and I to do a remote session so you can see what's happening directly? There's just no real way for me to say do this, this and this to reproduce it.
I've also got another random issue going on with EF Core since the upgrade to 3.0, referenced here: https://github.com/aspnet/EntityFrameworkCore/issues/18145. It's possible the two are somehow related? I tried making a slimmed down sample solution following my structure as close as possible, and I can't reproduce it. The only difference is that the sample solution started out as 3.0 from the beginning and wasn't upgraded from 2.2.
Somehow I have a feeling that the real fix will be for me to start a new 3.0 solution and copy everything over from the current solution, but that just sounds like a nightmare and makes no guarantees that with any other future version I won't have the same problem when upgrading.

Two weeks into this, I have discovered a few things, mostly that I am SoL.
First, I decided to create a new .NET Core 3.0 solution and I spent three days copying the code to it. That didn't help at all.
Second, I made a VirtualBox VM and installed a fresh copy of Visual Studio 16.3.4 to it. After running it the issue was no longer there, so it looks like the conclusion is that VS is messed up. I guess having VS 2013, 2017, and 2019, and constantly patching them is bound to cause incompatibility.
I would use the VM to continue development, but it seems that performance is real bad even though its on an i7-4790K, and an EVO 970 M.2... Also, since the solution starts up four Gulp watch tasks, each one likes to use 25% of the CPU for some reason (thanks Node) so just sitting idle the VM is using 100% of the CPU. Probably has something to do with the storage being virtualized. I would try Hyper-V, but even though I install it, the management console is missing, so SoL there too. Yay!
Honestly, VS 2019 seems be at the root of the issue, and frankly it seems to have regressed in stability vs 2017. Besides all of the issues I've been having above, IntelliSense never works anymore, and I constantly get yellow bars telling me some component has crashed, like say renaming a file.
The real solution it seems is to do a fresh install of my entire computer, which is something I don't have the time for. I've already wasted far too many days trying to figure out and fix tooling and framework problems rather than actually developing the project that has a month left to release...
// rage quit

I went through the process of reinstalling Windows, Visual Studio and everything else on my computer earlier this week. I installed VS 16.3.4 and it seemed to resolve the issue... until VS 16.3.5 update came out two days later and the issue is back. So... It seems to point once again at an incompatibility between VS and .NET Core 3.0, especially as VS updates.

So, I've been living around this issue by hacking the project file every time it threw, but yesterday it decided to rear its ugly head on the published version. I've finally resolved it by using more hacks. I took advantage of my Gulp configuration to watch the project that has the Razor views, and if they change to copy them to the project that's actually using them. This way they're compiled along with the other views in the project and everything works fine.
The conclusion is that in .NET Core 3.0 generally on first run additional view DLLs are not being loaded and thus the views in them are never found. I don't know if it's a runtime issue or something else, but it's exists. I also don't know if Razor Class Libraries are affected, since I'm not using one instead opting for an ASP.NET Core app set to compile as a library.


WIP: switch AWS clients over to a generic cloud client library so it can run on other locations.

I haven't actually tried this out yet, and probably won't be able to on AWS since I don't have an AWS account. I'll get it running on GCP today though.

OK, this is working now for GCP. The instructions to setup need to change a bit, the main difference is the environment variables used to access the queue/storage. They basically follow the patterns from here: https://github.com/google/go-cloud
For GCP, you can use something like:
OSSMALWARE_UPLOAD_BUCKET_URL=gs://<gcs bucket name>
OSSMALWARE_QUEUE_URL=gcppubsub://projects/<gcp project id>/subscriptions/<gcp pubsub subscription>

For AWS, it would look like:
OSSMALWARE_UPLOAD_BUCKET_URL=s3://<s3 bucket name>
OSSMALWARE_QUEUE_URL=awssqs://sqs.us-east-2.amazonaws.com/123456789012/myqueue

Also, one more thing: we'll need to update the log line here since it previously pointed to the bucket URL and now points to the bucket object:
2020/11/26 03:35:10 uploading /home/ec2-user/pypi-0-._.-._.-._.-._.-._.-._.-0-0.1.scap to &{%!s(*s3blob.bucket=&{oss-malware-results 0xc00000e168 false}) %!s(*oc.Tracer=&{gocloud.dev/blob gocloud.dev/blob/s3blob 0xc00000e040}) {{%!s(int32=0) %!s(uint32=0)} %!s(uint32=0) %!s(uint32=0) %!s(int32=0) %!s(int32=0)} %!s(bool=false)}/pypi/pypi-0-._.-._.-._.-._.-._.-._.-0-0.1/pypi-0-._.-._.-._.-._.-._.-._.-0-0.1.scap

Otherwise, this seems to work fine on AWS, too, which is great!

Ready for another look!

All set!


Full Screen Material Dialog

Can we open open this material dialog in fullscreen !

No, not with this library.

Just use an Activity.


Pull ip addresses out of configs

We should rely on /etc/hosts entries to turn fqdns into undercloud
floating IPs, to bypass upstream gateways when communicating within the
cloud.

retest

retest

:+1: looks good. consistent with this – https://github.com/blueboxgroup/ursula/pull/1376

:+1:


Feat/jwt authentication

Description
This pull request adds the option of sign in using JWT instead of session cookies.
Users can now pass the an authentication method to SSXServer constructor, which will tell the login route which type of authentication should be forward to the client, once the nonce signature is validated.
The signingKey prop from SSXServer was reused to server as private key to the sign method from jsonwebtoken lib.
Nothing was changed on the /ssx-nonce route, since session is still being used to record users nonce during the login process. The difference is that we now call req.session.destroy on /ssx-login route if authentication method is JWT and the login was successful, therefore no further session will be needed, all auth data will live on the client.
Also, /ssx-logout stays the same, because as mentioned above, the auth data lives on the client-side, therefore the there's nothing we have to do about that on the server.
This PR only provides support for express so far. Once we agree on the details of the implementation I'll implement for http package as well
Type

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

System Configuration
(Please delete options that are not relevant)
Runtime version(s):
Browser version(s):
Firmware version(s):
SDK version(s):
Diligence Checklist
(Please delete options that are not relevant)

[x] This change requires a documentation update
[x] I have included unit tests
[ ] I have updated and/or included new integration tests
[ ] I have updated and/or included new end-to-end tests
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] Any dependent changes have been merged and published in downstream modules

Hey @iankressin, I reviewed your work so far and it looks like you've made really great progress! I  just wanted to check in with you to see how things are going on the ticket. Please feel free to reach out if you are blocked or otherwise want to chat about the implementation

Hey @iankressin, I reviewed your work so far and it looks like you've made really great progress! I just wanted to check in with you to see how things are going on the ticket. Please feel free to reach out if you are blocked or otherwise want to chat about the implementation

Hey @franklovefrank! I just start to work on the http implementation and also fixed the issues @44203 pointed out. It's likely that the PR will be ready for another round of review late next week

Hi, I see this PR was marked as a draft, but wanted to take a quick look and leave a couple notes and check in to see if you need any support getting tests and CI passing and ready for review!

I guess I can your help right now.
I'm trying to test write a unity test for the http implementation method that looks like this:
describe.only('Should log in using JWT and COOKIES', () => {
  const ssx = new SSXServer({
    signingKey: 'FAKESIGNINKEY',
    authenticationMethod: SSXAuthenticationMethod.JWT,
  });
  const ssxMiddleware = SSXHttpMiddleware(ssx);
  const app = http.createServer(ssxMiddleware());

  test('Should receive JWT in response of a successful log in', async () => {
    const res = await request(app).post('/ssx-login').send({
      siwe: SIWE_MESSAGE,
      signature: SIGNATURE,
      daoLogin: false,
      resolveEns: false,
    });

    expect(res.statusCode).toEqual(200);
  });
});

And I get and error back saying:

'Expected the field nonce to be set on this session.'

Which makes a lot of sense since I'm not calling /ssx-nonce before. So the question is: is there anyway of mocking the session for the http implementation?

hey ian! you can look at an example of mocking the nonce in the tests here https://github.com/spruceid/ssx/pull/128/commits/f8fc04d8f65f0ff58154b0473446a2cd7b11bbd4#diff-cd43c404c5fe37cbc7ea653c3cc90034d684397c500d227f536702dde74c044 . let me know if this helps

hey ian! you can look at an example of mocking the nonce in the tests here f8fc04d#diff-cd43c404c5fe37cbc7ea653c3cc90034d684397c500d227f536702dde74c044 . let me know if this helps

Thanks @franklovefrank I'll take a look into that!


make oracle-installcheck fail

Bug Report
make oracle-installcheck fail
IvorySQL Version
IvorySQL master
OS Version (uname -a)
centOS 7
Current Behavior
make oracle-installcheck fail

Expected behavior/code
Success
Step to reproduce
pg_ctl ../data start
make oracle-installcheck

#542 #543


[ACR] Add "unknown" to enums

Data Plane API - Pull Request
There's a new value "unknown" introduced to enum ArtifactArchitecture and ArtifactOperatingSystem, this PR adding the new value to our known value list.
API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

Link to API Spec engagement record issue: N/A

Is this review for (select one):

[ ] a private preview
[ ] a public preview
[ ] GA release

Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified. Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.

Design Document:
Previous API Spec Doc:
Updated paths:

❔Got questions? Need additional info?? We are here to help!

 Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

💬 Teams Channel
💌 email

Click here for links to tools, specs, guidelines & other good stuff
Tooling

Open API validation tools were run on this PR. Go here to see how to fix errors
Spectral Linting
Open API Hub

Guidelines & Specifications

Azure REST API Guidelines
OpenAPI Style Guidelines
Azure Breaking Change Policy

Helpful Links

Azure DevTools Wiki

Close it as we decided to not updating swaggers so that will not bring extra costs across languages in sdk. cc: @pallavit

Thank you @YalinLi0312


purge: add initial playbook

This playbook is intended for purging a whole Ceph cluster
Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1881192
Signed-off-by: Guillaume Abrioux<EMAIL_ADDRESS>

note to myself: still missing some tests after purge playbook is done


Crypto code review for Encrypt-then-MAC

This is a toy crypto code review dry run before moving to the actual mitls-fstar code.
I started here:
https://github.com/FStarLang/FStar/commit/e332dcdd7a550bf0d299c0046775ad17da7134bd#diff-cee8a994ca6ba2935092daec16ed7939R90
List of commits is here:
https://github.com/FStarLang/FStar/commits/master/examples/crypto/EtM.AE.fst
Please discuss the code in the diff and sign off once you are happy:

[ ] Markulf
[ ] Cedric
[ ] Antoine
[ ] Santiago

Now there are also explanations in the tutorial. The code is not yet moved, and I did not come up with good exercises for the tutorial yet.

hopefully being in the tutorial will give the code more visibility, closing this issue for now


Suggestions for cross compiling to armv7-unknown-linux-gnueabihf

cargo build works correctly on my host using features=["openblas"]. However, when cross compiling to armv7-unknown-linux-gnueabihf, I get the following (truncated) error:
error: linking with `arm-linux-gnueabihf-gcc` failed: exit code: 1
= note: /target/armv7-unknown-linux-gnueabihf/debug/deps/libopenblas_src-75b3c950014242b8.rlib: error adding symbols: File format not recognized

I assumed the openblas-src crate would have taken care of acquiring the correct armv7 libs, but it looks like I'm mistaken. Any suggestions? Should I take my question to openblas-src?

I just found that there's an old issue https://github.com/cmr/openblas-src/issues/6 about this. I'm going to investigate fixing this in openblas. Will leave this open for now in case anyone else wants to chime in.

I've submitted a PR to openblas-src: https://github.com/cmr/openblas-src/pull/26. I'll close this issue once it's been merged.

Merged!


Unable to push to PMP

Attempting to save a Post: http://wordpress.pmpdev.org/?p=66
When I click "Update and push to PMP", the changes to the WP Post are saved.  But I'm sent to a blank white screen, and the content does NOT make it to the PMP.  PHP log shows:
[Mon Apr 20 15:07:59 2015] [error] [client <IP_ADDRESS>] PHP Fatal error:  Call to undefined method stdClass::save() in /var/www/html/wp-content/plugins/pmp-wordpress-master/inc/functions.php on line 250, referer: http://wordpress.pmpdev.org/wp-admin/post.php?post=66&action=edit

Any ideas?

Update: this seems tied to which featured image I pick.

Picking a featured-image downloaded by a previous version of the plugin

I get that Call to undefined method stdClass::save() error

Picking a featured-image downloaded by the current-master version of the plugin

I get a Uncaught Pmp\\Sdk\\Exception\\NotFoundException: [403]: Forbidden error
Happens when the plugin attempts to PUT an image-doc that I don't own (it's the image that was pulled down from the PMP`

Picking a featured-image that I uploaded

Works fine

Are featured images tied to the Post, or the Media item?  I'm sort of thinking they should be tied to the specific Post.
For instance, I create 2 Posts using the same featured image from my Media Library.  After pushing both Posts to the PMP, I should end up with 2 Story-docs and 2 Image-docs in the PMP.  If I change the featured image on one Post, it should just update 1 of those existing Image-docs to have different enclosure links.

Couple things:

We can try filtering the media picker so that images that you do not own are not available to link with stories/posts. This seems like it might be an edge case, but filtering the list may be easy enough that we should just do it. This should fix numbers 1 and 2 in your comment above.
Regarding the relationships between media and story docs -- I think creating a new Doc each time an image is attached to a story will cause problems unless we actually duplicate the image in WordPress so that it can be assigned its own PMP GUID. Maybe we need to take it a step further and filter out ANY images that have been attached to posts and pushed to the PMP. Users would then have to re-upload an image to attach it to a post. This would ensure a unique image-to-post relationship on both the WP and PMP sides.

I managed to set up a filter for the media library, which will exclude any media items that exist in the PMP and do not belong to the current user. See: 5430e961d7a7b0eb985046c7de1bfa3d3e62a4d7. This should mean the original issue of being unable to push to PMP is fixed.
Perhaps we should open a new ticket for more discussion around the other issues?

Agreed.  Opened #57.


Allow dynamic redirect_uri

This pr makes redirect urls possible. Assume our auth endpoint is /horizon/github, when a user clicks:

/horizon/github?redirect_uri=/abc, browser will redirect to /abc on login success
/horizon/github, browser will redirect to default success url ( the entry auth_redirect defined in .hz/config.toml

This change is

I have a requirement that A user should be redirected to the previous page where he clicks the login button. Since the login button is present on all pages,  the auth_redirect entry does not help.

ping @Tryneus

Hey @Youmoo, just wanted to say we'll be looking at this soon. Thanks for your patience and for submitting the PR!

As it stands, this is a massive security vulnerability.  This could be acceptable if we restrict the redirect URI to only the current host, but even that could be vulnerable for certain applications.
The scenario is a CSRF, and unfolds like this:

Application is hosted on a webserver: https://app/
Victim has an account with Application, authorized using Oauth provider X
Attacker owns a webserver: http://fake/
Attacker gets a victim to follow a link to the application and log in: https://app/horizon/x?redirect_uri=http://fake/
Victim is automatically logged in because Application is already approved with the provider X
Victim is redirected to Attacker's webserver with the token as a query parameter
Attacker now has Victim's token and can now issue commands as that user until the token expires or is invalidated

We've discussed reworking how tokens are passed back to the browser in a different way - and it might be done such that we can allow something like this (see #492).  As it stands, we can't use this code though.  Thanks for the suggestion, though, @Youmoo!

A CORS-like system can be used to provide secure filtering of dynamic redirects.  This is highly needed for development when the client and server sides are often developed in different environments by different people.  It is also useful so that the front-end web apps and database/server API can be in different places.


support for joj.sk site

[x] I've verified and I assure that I'm running youtube-dl 2016.03.27

Before submitting an issue make sure you have:

[X] At least skimmed through README and most notably FAQ and BUGS sections
[X] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[X] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

Example URLs

Single video: http://dizajn.joj.sk/nove-byvanie-dizajn-archiv/2016-03-06-nove-byvanie-dizajn-premiera.html
Single video: http://zoo.joj.sk/zoo-epizody/2016-03-23-zoo.html

JOJ archive is supported, but it seems these videos are not downloadable using youtube-dl (version 2019.06.27)
New links for videos in question are:

https://videoportal.joj.sk/nove-byvanie-dizajn/epizoda/29609-nove-byvanie-dizajn-9-flat-gallery
https://videoportal.joj.sk/zoo/epizoda/29911-zoo-38

(Videos compared by date.)


Missing data context in args.data since 1.7.0

Reported on community
Repro:
<App>

  <JavaScript>
    function menuButtonClicked(args) {
      console.log("args = " + JSON.stringify(args));
      console.log("testvar = " + args.data.text.value);
    }

    module.exports = {
      menuButtonClicked: menuButtonClicked
    }
  </JavaScript>

  <ClientPanel>
    <MenuItem Label="Demo123" Clicked="{menuButtonClicked}">
    </MenuItem>
  </ClientPanel>

  <Rectangle ux:Class="MenuItem" Row="0" Column="0" Color="#030303">
    <string ux:Property="Label"/>

    <JavaScript>
      var Observable = require("FuseJS/Observable");
      var text = this.Label.map(x => 'Label: ' + x);
      module.exports = {
        text: text
      }
    </JavaScript>

    <StackPanel>
      <Text
        Background="#f00"
        Color="#fff"
        FontSize="22"
        Alignment="Center"
        Margin="0,0,0,100"
        Value="{text}">
      </Text>
    </StackPanel>
  </Rectangle>

</App>

The MenuItem component exposes a data context that holds a text variable, which in theory should be available outside of it. Or, at least, it was until 1.7.0.
User reports this works as expected on 1.4, 1.6.0 and 1.6.1, and fails on builds after 1.7, including 1.8 QA.
Affected: local preview on both Windows and macOS. Haven't tested mobile targets.

The forum thread Click handler arguments suddenly undefiend posted by Wodger was linked to this issue.

This looks like it was relying on an undefined behaviour of context binding in previous releases. The binding to JavaScript in this manner was not intended and was causing some defects that needed to be fixed.
To get a context you must use an Each, Instance, With, or a PageControl or Navigator with page contexts.

Closing ticket, since the cause of this issue was a deliberate and necessary change.


(Do not merge yet) Update kedro-datasets optional dependecies requirements naming

Motivation and Context

Part of the proposal for https://github.com/kedro-org/kedro-plugins/issues/313. To be merged after kedro-datasets 3.0.0 release. Updates the requirements for starters to use the new naming convention for kedro-datasets optional dependencies.
Depends on https://github.com/kedro-org/kedro-plugins/pull/570
How has this been tested?

Checklist

[ ] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[ ] Assigned myself to the PR
[ ] Added tests to cover my changes

Tests are expected to fail until the kedro-datasets 3.0.0 release.


[Do Not Merge] Distributed Availability Groups API

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[x] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month. 1. of October
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month. 1. of October
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that label “WaitForARMFeedback” will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

LGTM

the SDK breaking change was not introduced by this PR
the systemData is not supported by SQL now. thus, we can ignore the SwaggerLintDiff error

Don't merge it now.
we will wait this feature was deployed to at least one prod region.

For new RP/API meeting with ARM team is required to review the API surface area; please share the following to continue
a. Scenario overview
b. API Model (object/resources)
c. Flow of the scenario through the API
If the meeting is already done please share the details.

@chiragg4u This API is not new, but basically the rename of the API which passed the review. Adding @ericshape who approved the change.

close due to we have another all-in-one PR to cover it: #16184


feat(solidjs): Create main layout(gists + top repos)

Acceptance Criteria

[x]  2 column layout
- [ ]  Left side
- [ ]  gists panel
[x]  Right side
- [ ]  Top repositories title
- [ ]  card for each of the users’ top repos
[x]  view all repositories button that navigates to user profile page

Closes: #691
Preview

There is a ticket for creating the RepoCard component. I think this PR went out of scope.
Also, about the style, did we decide to place them in a different file?

yes, makes sense @vyktoremario, think in the moment I started to work on this, the other ticket wasn't merged yet, that's why. Will remove that. Thanks!! :)

I left a comment.
Also, I saw that some index.js files were deleted, is there a reason for this?

In most cases an index file that re-exports the entire directory is not needed. Generally imports should from the file directly. I think one of the main exceptions to this is a directory that is a single component but includes files for other things like tests etc.


Updated .travis.yml

This lets you use the Docker container infrastructure on Travis which has a much faster queue and performance. :)

Hi @googlebot -- I signed the CLA.

I would like to see this merged if possible as slow Kubernetes builds are making my builds take a long time to start.

This LGTM, will merge once travis is green.


Relationship to PROV-O

Not for the first version, but it would be interesting to think about how SSSOM relates to PROV-O.  e.g. would mappings have prov:wasGeneratedBy properties?  could ontology alignment be a prov:Activity?

Yes, looking at how to best capture provenance is important. In the Open PHACTS project, we used VoID for that. You really want to capture more detail like who captures this, using what, from what, when, and using which versions. Typically that will be layered. Like these mappings were created based on the mappings available at that resource, and the resource itself should indicate how they created those.

Some examples from slack convo with @cmungall  mymappings was-generated-by [a CurationActivity; timestarted...]

Some examples from slack convo with @cmungall  mymappings was-generated-by [a CurationActivity; timestarted...]

Would someone be able to work on this? I think concretely, it would be nice to at least document how the two relate, perhaps even implement them in sssom-py

I have to review PROV-O from a process ontology development angle.  But to be of help with respect to SSSOM, I'd need to read a 2 pager on what SSSOM goals/capabilities are, down to the entity type - is there such at thing?  Is the question what OBOFoundry entities map to PROV-O, or what data structure PROV-O has that SSSOM needs?

pls assign (at least one person anyway) to @mbrush

I'll note that my PROV-O review is limited to process related terms, but SOSA is also reviewed in the same light, both with respect to OBO in this table.  It reveals mapping cases that it sounds like SSSOM strives to describe.

The task for the workshop is to determine which properties and best practices from PROV should be adopted in SSSOM, and which SSSOM metadata elements should be mapped to prov: metadata elements. Overall, we need to ensure that we can model mapping provenance in a standard, reliable (yet minimal) way, and we have not missed anything important.

Proposal below. The essence is to allow granularity where people need it, and to keep the sssom tsv simple, with the most useful parts of the prov payload denormalized as sssom fields.

Add an optional column was_generated_by, with slot_uri pointing to the prov property
The range of this would be a CURIE denoting a (named) instance of a prov activity
The CURIE prefix MUST be registered in the header
the expanded URL SHOULD resolve, and MAY resolve to both computable and human readable info via conneg
the prov activity MAY be included as YAML-LD in the header
If a prov activity is provided, it must be consistent with the projected sssom fields

mapping_tool = activity.wasAssociatedWith, range SoftwareAgent
creator_id = activity.wasAssociatedWith, range Person
subj,obj source = activity.used
the prov object MAY include wasDerivedFrom between subj/obj sources and the sssom mapping set
etc

Hi all.  I don't have a deep understanding of the requirements/use cases related to provenance for SSSOM, but Chris' proposal above sounds reasonable. Cant make the workshop, but happy to follow up later and review any concrete examples/proposals that come out of it.

Other impressions from workshop:

Look at vocabs like https://github.com/sifrproject/MOD-Ontology/blob/master/mod-v1.4_properties_template.ttl  for properties commonly used
There are perhaps multiple activities involved here:

mapping creation
mapping review
mapping reconciliation (activity on mapping set level)

Define Inputs and outputs of activities?
(Will add more in a bit)

from @graybeal

Check 20-30 provenance related properties that could be relevant: list

list of most-recommended terms as a template: https://github.com/sifrproject/MOD-Ontology/blob/master/mod-v1.4_properties_template.ttl

This is now described in our recent OM 2022 report. The gist: the mapping_justification is a PROV:Activity that confirms/generates the Mapping. Agents acting on Mappings include people (author_id) and tools (mapping_tool).


Fix compatibility with datejs

Fixes compatibility with datejs (or any other library that adds a toObject method to the Date prototype).
The fix ensures that mongoose ignores toObject methods for the standard types "Date", "Function" and "Regex" (these were currently checked for after looking for a toObject method).
This fix addresses issue #502.

the only problem with this is that it still breaks when someone does Object.prototype.toObject = function (){} but its better than nothing.
I'll test / merge later today. thanks!

I believe it will also cover that case. If the object is an instance of
Date, Function or Regex then it won't even look for, or call, the toObject
method.
I suppose the other primitive types could also be checked for, but that's
probably getting silly. People shouldn't be monkey-patching these things
anyway ;)
Question: you've done the type check by looking at the constructor name
(rather than instanceof) in clone, yet used instanceof in deepEqual. Any
particular reason? I just followed the same pattern.
chris
On Tuesday, December 13, 2011, Aaron Heckmann <
<EMAIL_ADDRESS>wrote:

the only problem with this is that it still breaks when someone does
Object.prototype.toObject = function (){} but its better than nothing.
I'll test / merge later today. thanks!

Reply to this email directly or view it on GitHub:
https://github.com/LearnBoost/mongoose/pull/646#issuecomment-3127075

tests fail
uncaught: AssertionError: expected 0 to equal 4
    at Object.equal (/home/aaron/test/mongoose/node_modules/should/lib/should.js:306:10)
    at Promise.<anonymous> (/home/aaron/test/mongoose/test/types.array.test.js:359:34)

Platform?  I can't reproduce.  I'm using master with only this pull request applied, and I've tried with both node 0.4.7 and node 0.6.5.
NPM details:
% npm ls
<EMAIL_ADDRESS>/Users/cleishma/work/mongoose
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

Ok - I started up a virtual box and debugged this.  There were a few other places in the code that assume a "toObject" method means that it's a   Updating the pull request with a fix.

PS. I'm starting to wonder if, perhaps, checking for toObject should be changed to checking for the types of Document or MongooseArray (rather than adding an additional check that it's not a primitive type, as this patch does).

merged #655 instead


openclarity-scan Job Uses amd64 Only Curl Image

My kubernetes cluster is a mix of amd64 and arm64 nodes. The openclarity-scan jobs use yauritux/busybox-curl:latest to download assets. That image is 2 years old and is only amd64.
https://github.com/openclarity/openclarity/blob/9e20b24d929dd0a4842a18f05f2e3658dd2c49fd/provider/kubernetes/scanner/scanner.go#L189
I don't have a way to test another image but I would imagine the official curlimages/curl image would work?

Hi @duckman, thanks for raising this. We will have this resolved in the next patch release


Bug: single-click interactions require double-click

Hi there,
Great project. Really appreciate the opportunity to use web standard technology to make native Mac apps. :)
To reproduce the bug:

Click the "Play" button in Xcode. Xcode builds Quark Shell and automatically gives it focus.
Click on a different app (e.g., Xcode, Chrome) to give that app focus.
Click the Quark Shell app icon in the status bar again. Now it takes a double-click to interact with buttons instead of the expected single click. For example, I don't see a notification appear on my screen unless I double click the "Notification" button.

This problem doesn't arise if you click the Quark Shell app icon immediately after clicking the play button. This makes me think the bug appears when you click the Quark Shell app icon while another app has focus.
If you have any trouble reproducing the bug, let me know. I'd be happy to make a screencast or something.

Sorry I can't reproduce the issue, can you elaborate more or make a screencast? Thanks!

Sure. Here's the screencast:
https://youtu.be/5ugnxxCsb6Q
It includes annotations explaining the problem.

Meant to include this earlier. System details:

@ctbailey: I get your point, but still can’t reproduce. I’m running 10.10.3 on exactly the same hardware. Have you installed any window/menubar management software?

Just upgraded to 10.10.3 and the problem went away.
I was getting this issue even when the project was exported from Xcode, though, so this would still affect users running earlier versions of OS X.

There's a chance it was an issue in Xcode or something that was resolved by the OS update.

Thanks for the reply. Then I’d close this issue since it was an Apple issue and has already been resolved.

I don't think this issue should be closed. We only know it's resolved for users of 10.10.3. There's no guarantee that apps exported from Xcode on 10.10.3 will work properly on 10.10.2. We need to test that.

Do you still have any 10.10.2 machines?

I don’t think we have enough bandwidth to support all the old minor versions. As 10.10.5 has already been released, I’m closing this.


fix: rm tmp if it exists

Description
Conditionally remove tmp file when running prepare-for-codreview
Motivation and Context
The first time running just prepare-for-codereview errors because we try to remove the tmp file. This change just checks if that dir exists before removing it.
How Has This Been Tested?
Manual tests
Screenshots (if appropriate):
Types of changes

[x] Chore (a change that does not modify the application functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] Documentation updates are needed, and have been made accordingly.
[ ] I have added and/or updated tests to cover my changes.
[x] All new and existing tests passed.
[ ] My changes include a database migration.

This fixed the issues I was seeing with the missing tmp directory. However, after progressing further I ran into another error:
{"level":"fatal","time":"2024-04-17T12:35:58.048217-04:00","message":"Failed to run command `show`: changes detected in git repository"}
exit status 1
error: Recipe `stbernard` failed on line 18 with exit code 1
error: Recipe `show` failed on line 34 with exit code 1
error: Recipe `_prep-steps` failed on line 60 with exit code 1
For more details, see output files in /Users/jbarnett/dev/bloodhound-enterprise/tmp

After some discussion, this is an intended error to ensure the developer addresses all uncommitted files. This helps handle situations when the license checker finds files that need updated. @benwaples is going to add some additional wording here to make this error less ambiguous.


Trunk v0.18.0 breaks <script data-trunk ...> in release builds.

Trunk v0.18.0 adds minification to assets, however it appears to be overly aggressive, and can break release builds.
The Trunk documentation says "Trunk will copy script files found in the source HTML without content modification. This content is hashed for cache control. The src attribute must be included in the script pointing to the script file to be processed."
Since the documentation doesn't say anything about dealing with JavaScript Modules, I decided to rely on the "without content modification" bit and just include external scripts (in my case highlight.js) as normal JS bundles in global scope. However, when running a release build with Trunk v0.18.0, my code that depends on hljs existing fails.
I get one error from HLJS when the script tag for the hljs file is reached:
Uncaught TypeError: a.registerLanguage is not a function
    <anonymous> http://localhost:8080/highlight.min-4ab3438c95a09b70.js:1
    <anonymous> http://localhost:8080/highlight.min-4ab3438c95a09b70.js:1

And then another error when I then try to call it using wasm-bindgen:
Uncaught ReferenceError: hljs is not defined
   [... snip ...]

I have created a minimal sample project that demonstrates the issue at https://github.com/zstewar1/trunk-broken
If I run the sample with trunk serve or trunk serve --release with trunk 0.17.5, I get no errors and the code get highlighted correctly.
With trunk 0.18.0, in debug mode with trunk serve, the code highlighting still works. However in release mode, trunk serve --release, the project breaks. There is no highlighting and the aforementioned errors show up in the web console.
My workaround for now is simply to revert to trunk 0.17.5.

It is using minify-js for this. So I am not sure we can do much about that. However, what we could do is to add an attribute, allowing to disable minification for certain assets. And a config switch to disable it entirely. … And fix the docs on that :)

Hm, that's interesting. I think being able to disable this is a good first step. What would also help is to have a simple reproducer for this.

Thanks @zstewar1 … you pointed me into the right direction. I added some evaluation of the type attribute. Extended the vanilla example with:
    <script data-trunk src="src/script.js"></script>
    <script data-trunk src="src/script.mjs" type="module"></script>

Which then results in:
var testFromJavaScript=(()=>{console.log(`Hello from JavaScript`)})

And:
var a=(()=>{console.log(`Hello from JavaScript Module`)});export{a as testFromJavaScriptModule}

Which looks exactly what you reported. And which seems to work now (first one keeps the global variable name).


Consolidate UICatalog tests to cut down on time outs

All the tests remain, but session creation is minimized.

again will trust you on the details here. +1 for shorter tests!

UICatalog tests from 40 to 16-18 minutes!


We should move out from our own Spark-Java to something better

This looks promising.
https://github.com/intellisrc/spark

Tried this, not well tested, Cowj test fails on this version.


Verify that the GET /v2/catalog call is aligned with CF's definition

https://docs.cloudfoundry.org/services/api.html
this is on the call from the service registry to a service broker

add unit testcases too

#dibs


Add buffer barriers to "Usage in frame" view

Description
This is very helpful to debug missing barriers by matching the workflow offered for images.

Oups, sorry about that!

I manually merged this, and squashed the formatting into the original commit. FYI for future reference, I prefer not to have formatting commits in the history, see CONTRIBUTING.md for more info.


在build的时候出现的问题

ERROR [karton-logger  4/14] RUN GOBIN=/usr/local/bin/ go install

Hello,
please provide more information about the error that occured. For example, would it be possible to provide full Docker build logs?

=> ERROR [karton-logger  4/14] RUN GOBIN=/usr/local/bin/ go install   21.9s

[karton-logger  4/14] RUN GOBIN=/usr/local/bin/ go install<EMAIL_ADDRESS>&&     GOBIN=/usr/local/bin/ go install<EMAIL_ADDRESS>&&     GOBIN=/usr/local/bin/ go install<EMAIL_ADDRESS>21.90 go<EMAIL_ADDRESS><EMAIL_ADDRESS>Get<EMAIL_ADDRESS>dial tcp <IP_ADDRESS>:443: connect: connection refused

failed to solve: executor failed running [/bin/sh -c GOBIN=/usr/local/bin/ go install<EMAIL_ADDRESS>&&     GOBIN=/usr/local/bin/ go install<EMAIL_ADDRESS>&&     GOBIN=/usr/local/bin/ go install<EMAIL_ADDRESS>exit code: 1

你好，
请提供有关所发生错误的更多信息。例如，是否可以提供完整的 Docker 构建日志？

 Are you by any chance behind a firewall?

Closing due to inactivity


Add button to clear search form

Description of change

Add a button-styled link that 'clears' the search by reloading the page without search parameters.

Story Link
https://trello.com/c/ScrpaQJD/1162-add-a-clear-button-to-delete-the-text-in-the-search-box
Screenshot

Only clears, after you've done a search.
If you haven't done a search it doesn't clear.

Visit search page
Enter any text
Change your mind!
Select "clear search"
I does not clear.... but I expect it to clear.

Only clears, after you've done a search. If you haven't done a search it doesn't clear.

Visit search page
Enter any text
Change your mind! press nothing yet
Select "clear search"
I does not clear.... but I expect it to clear.

Hmmm....interesting problem! A link to the existing url won't refresh the page. I guess will need a bit of javascript 🤔


bug: Chart inside Dialog

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
after update the Charts for .NET 7, I started have problems to open the charts on a dialog, when is on the page, its works, but if some problems, on a Dialog its not working or taking so long to open.
I saw also that on a page, if the chart is not load on the first load, sometimes doesnt load.
Example, if a show the chart after select a item on the table, the chart is not loading, but if I the chart is opened before, like a fake chart and change the data after the select is working good.
I cant tell which version started have problems, because since the begin of the year that was working normally and last month I upgrade the project for .net 7.
Thank you very much
Expected Behavior
No response
Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version
.NET 7
Anything else?
No response

@gmondin Hi. could you provider a demo that Chart component on a Dialog?

I made like this and has the same problem, example:

@_LocalLocalizer[nameof(Dynamic.Dashboard.Shared.Resources.Resource.Test)]

@code {
private bool _collapsed = true; //if I started collapsed, the chart is not showing or sometimes show but after take more than minute, if I started uncollapsed, the chart is showing normally, independent if I have selected or not on the grid
private Random Randomer { get; } = new ();
private int LineDatasetCount = 2;

private int LineDataCount = 7;

private Task<ChartDataSource> OnInit(float tension, bool hasNull)
{
    var ds = new ChartDataSource();
    ds.Options.Title = "Line Chart";
    ds.Options.X.Title = "days";
    ds.Options.Y.Title = "Numerical value";
    ds.Labels = Enumerable.Range(1, LineDataCount).Select(i => i.ToString());
    for (var index = 0; index < LineDatasetCount; index++)
    {
        ds.Data.Add(new ChartDataset()
        {
            Tension = tension,
            Label = $"Set {index}",
            Data = Enumerable.Range(1, LineDataCount).Select((i, index) => (index == 2 && hasNull) ? null! : (object)Randomer.Next(20, 37))
        });
    }
    return Task.FromResult(ds);
}

}

@gmondin could you provider a full demo project?

@gmondin no response auto close issue


Simplify AVar JS

Is there a reason not to just enqueue the values like this, rather than having an array of producers? Also dropped the {} for unit, as that's unnecessary now.

I think its so that we could at some point have putVar block until the value was taken (to work like MVars, and not like a queue). However, we haven't ever done that, and doing that now may open up a can of worms. @jdegoes?

Yeah, ultimately I'd like AVar to work like MVar. It is a change in semantics, may deadlock or otherwise change behavior in code — needs to be thought through.

If we were going to do that, I think we'd probably want to introduce an alternative type. We rely upon the current AVar semantics in multiple places, and not just in SlamData.


Link to index.ios.js in the readme is bad

Link to index.ios.js in the readme is bad

Thanks, my mistake I renamed the file.
This is fixed :+1:


Timeout for NTP request

When send many NTP request we may catch package KoD
And next request on the same address along some time may have not respond. So NTP request may infinitely awaiting response.
Maybe should make timeout logic ?

fixed

fixed


Enable models from dbt_project.yml

We're updating our docs on packages, and wanted to include an example of how to write models for multiple warehouses. I got this to work locally, so wanted to contribute it back in case it's useful. No pressure to merge it soon — just wanted to share :)

lol guess I should have turned off my whitespace checking!

Looks great, thanks @clrcrl


WIP - Use String for serialization (for PR #278)

We need a separate JsonSerializer that abstracts writing out keys and deals with interpolation (we currently don't do proper string interpolation).


Update modules to use eve/api instead of eve/sdk

This should make make proto-vendor work correctly on pillar.

cc @nordmark @rvs

LGTM. Let me merge it shortly so I can rebase my PR on top of it.


False positive

<NBSP>:<space>:: is OK but padpo tells some problem about NBSP

Beware, <space>:: is valid, even mandatory, when prefixed by a dot, see 41d0079abcccfbf12461f8734f5158082a6a559a in python-docs-fr.
Because blah blah.<NBSP>:: is rendered as blah blah. :.

Yes you're right! As well after a ? or a !.
@JulienPalard Do you see any other mandatory cases?

Not at this time.

@JulienPalard OK, thanks!


[Question] Publishers.Sequence?

I think Publishers.Sequence is equal Observable.from.
Publishers.Sequence argument conform Sequence.
And Observable.from is the same
But Observable.of isn't the same.
    public static func from<Sequence>(_ sequence: Sequence, scheduler: RxSwift.ImmediateSchedulerType = CurrentThreadScheduler.instance) -> RxSwift.Observable<Self.Element> where Sequence : Sequence, Self.Element == Sequence.Element

    public static func of(_ elements: Self.Element..., scheduler: RxSwift.ImmediateSchedulerType = CurrentThreadScheduler.instance) -> RxSwift.Observable<Self.Element>

Yup, I think from does seem similar to Sequence.publisher. Happy to accept a PR.


✨ Add aria-label to Gallery and Discord icons

Summary by Sourcery
Enhance accessibility by adding aria-label attributes to the Gallery and Discord icons in the navbar.
New Features:

Add aria-label attributes to the Gallery and Discord icons in the navbar for improved accessibility.

@CodiumAI-Agent /improve