Skip to content

[blazor] Add parameter to ErrorBoundary to let it render ChildContent when an exception was thrown#66159

Open
zachneu wants to merge 4 commits into
dotnet:mainfrom
zachneu:ZN/ErrorBoundaryRenderContent
Open

[blazor] Add parameter to ErrorBoundary to let it render ChildContent when an exception was thrown#66159
zachneu wants to merge 4 commits into
dotnet:mainfrom
zachneu:ZN/ErrorBoundaryRenderContent

Merge branch 'main' into ZN/ErrorBoundaryRenderContent

ef472b7
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded Apr 22, 2026 in 0s

View the current status of Helix

Details

Pipeline Status

The list of queues is cached weekly. If your PR changes what queues your pipelines use, this information will not show the updated queues.

Estimated Pipeline Durations

This model assumes that the current state of the entire CI infrastructure is normal, and that your CI pipelines will succeed.

Pipeline Lower Bound Estimated Time Upper Bound
aspnetcore-template-tests-pr 1 hour, 23 minutes, 32 seconds 1 hour, 37 minutes, 13 seconds 1 hour, 50 minutes, 53 seconds
aspnetcore-components-e2e 1 hour, 13 seconds 1 hour, 5 minutes, 38 seconds 1 hour, 11 minutes, 3 seconds
aspnetcore-ci 41 minutes, 37 seconds 1 hour, 7 minutes, 47 seconds 1 hour, 33 minutes, 57 seconds

Highest Work Item Wait Time Queues

Here's a list of the top 3 queues with the highest work item wait time:

Queue Work Item Wait Time Difference in Moving Avg
ubuntu.2204.amd64.open 45 minutes, 39 seconds 0.19% 📈
windows.amd64.vs2026.pre.scout.open 25 minutes, 19 seconds -0.1% 📉
osx.15.amd64.open 23 minutes, 42 seconds -0.35% 📉

Grafana Dashboard

For more in-depth information on the status of Helix, visit our Grafana Dashboard.

Your Queues

☁️ Helix Queues

dotnet/aspnetcore is currently configured to submit to the following Helix queues:

🏢 On Premises Helix Queues

dotnet/aspnetcore uses the following on-prem queues:

Build Pools

Was this helpful? Yes No