Repository navigation
[release/13.6] metrics tree scroll issue fixed - #20762
Jose Perez Rodriguez (joperezr) merged 1 commit into
Conversation
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 20762Or
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 20762" |
Tests selector13 / 99 PR test projects · 2 PR jobs, from 1 changed file. Selected PR test projects (13 / 99)
Selected PR jobs (2)
How these were chosen — grouped by what changed
🔧 📦 affected project Job reasons
Selection computed for commit |
|
Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt. |
|
Retrying the failed CI jobs for this pull request from the CI run attempt. The rerun is being tracked in the rerun attempt. |
660f92c
into
release/13.6
|
✅ No documentation update needed. Step 5 branch taken: "excluded → backport" (exclusion_reasons: Triggered signals: none ( Evidence for exclusion:
This PR is a backport of #20758 (a CSS-only fix restoring |
Updated [Aspire.Hosting.Redis](https://github.com/microsoft/aspire) from 13.6.0 to 13.6.1. <details> <summary>Release notes</summary> _Sourced from [Aspire.Hosting.Redis's releases](https://github.com/microsoft/aspire/releases)._ ## 13.6.1 ## What's New in Aspire 13.6.1 Patch release for Aspire 13.6 that reduces dashboard CPU usage during sustained metric ingestion, restores scrolling in the Metrics tree, improves dashboard navigation, fixes container exec watch failures, and ensures session-scoped containers are cleaned up when stopping .NET AppHosts on Windows. ### 🐛 Fixes - 📊 **Dashboard CPU usage could increase during long-running metric ingestion** — Metric retention repeatedly scanned retained history on every insertion, causing steadily increasing CPU usage even with a fixed workload. Cleanup now skips dimensions below capacity and removes only the oldest surplus points when needed. Existing retention limits and exemplar behavior are unchanged, and no configuration changes are required. Regression introduced in 13.6. Fixes [#20725](microsoft/aspire#20725). ([#20747](microsoft/aspire#20747), backport of [#20736](microsoft/aspire#20736), @JamesNK) - 📈 **The Metrics tree could not be scrolled** — The meter and instrument tree now scrolls when it exceeds the viewport, allowing you to reach and select instruments below the fold. Regression introduced in 13.6. Fixes [#20728](microsoft/aspire#20728). ([#20762](microsoft/aspire#20762), backport of [#20758](microsoft/aspire#20758), @heyysiri) - 🧭 **Dashboard navigation could fail after a browser disconnect** — Pending page-state updates now persist session state before navigating and skip navigation when the browser has disconnected, avoiding an unhandled navigation failure. The navigation rail's overflow button also has consistent sizing, icon alignment, and hover styling in expanded and collapsed layouts and both light and dark themes. ([#20545](microsoft/aspire#20545), backport of [#20527](microsoft/aspire#20527), @JamesNK) - 🖥️ **Container exec watches could terminate shortly after AppHost startup** — A stalled DCP watch connection could produce a critical `Watch task over Kubernetes ContainerExec resources terminated unexpectedly` error and stop subsequent terminal state and log updates from being observed. Watch connection attempts now retry after timeouts, and periodic restarts correctly recreate connections without swallowing unrelated cancellation. Regression introduced in 13.6.0. ([#20664](microsoft/aspire#20664), backport of [#20466](microsoft/aspire#20466), @radical) - 🪟 **Session-scoped containers could remain running after stopping a .NET AppHost on Windows** — AppHosts launched through `dotnet run` or `dotnet watch` now allow DCP to finish resource cleanup during shutdown, including existing Ctrl+C and `aspire stop` flows. Persistent resources remain unaffected, while direct .NET launches and TypeScript/polyglot AppHosts retain their existing process protection. Fixes [#20495](microsoft/aspire#20495). ([#20514](microsoft/aspire#20514), backport of [#20494](microsoft/aspire#20494), @danegsta) --- *Full Changelog: [v13.6.0...v13.6.1](microsoft/aspire@v13.6.0...v13.6.1)* *Full commit: [3751e615ad660621f2a7aa4c390ef48e08a0eed8](microsoft/aspire@3751e615ad660621f2a7aa4c390ef48e08a0eed8)* Commits viewable in [compare view](microsoft/aspire@v13.6.0...v13.6.1). </details> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Updated [Aspire.Hosting.JavaScript](https://github.com/microsoft/aspire) from 13.6.0 to 13.6.3. <details> <summary>Release notes</summary> _Sourced from [Aspire.Hosting.JavaScript's releases](https://github.com/microsoft/aspire/releases)._ ## 13.6.2 *Full commit: [af07e33f8d1ef733645138b3f8e36067d073148d](microsoft/aspire@af07e33f8d1ef733645138b3f8e36067d073148d)* ## What's Changed * [release/13.6] Bump version to 13.6.2 by @danegsta with @Copilot in microsoft/aspire#20877 * [release/13.6] Pin MessagePack to 2.5.307 for security fixes by @eerhardt in microsoft/aspire#21156 **Full Changelog**: microsoft/aspire@v13.6.1...v13.6.2 ## 13.6.1 ## What's New in Aspire 13.6.1 Patch release for Aspire 13.6 that reduces dashboard CPU usage during sustained metric ingestion, restores scrolling in the Metrics tree, improves dashboard navigation, fixes container exec watch failures, and ensures session-scoped containers are cleaned up when stopping .NET AppHosts on Windows. ### 🐛 Fixes - 📊 **Dashboard CPU usage could increase during long-running metric ingestion** — Metric retention repeatedly scanned retained history on every insertion, causing steadily increasing CPU usage even with a fixed workload. Cleanup now skips dimensions below capacity and removes only the oldest surplus points when needed. Existing retention limits and exemplar behavior are unchanged, and no configuration changes are required. Regression introduced in 13.6. Fixes [#20725](microsoft/aspire#20725). ([#20747](microsoft/aspire#20747), backport of [#20736](microsoft/aspire#20736), @JamesNK) - 📈 **The Metrics tree could not be scrolled** — The meter and instrument tree now scrolls when it exceeds the viewport, allowing you to reach and select instruments below the fold. Regression introduced in 13.6. Fixes [#20728](microsoft/aspire#20728). ([#20762](microsoft/aspire#20762), backport of [#20758](microsoft/aspire#20758), @heyysiri) - 🧭 **Dashboard navigation could fail after a browser disconnect** — Pending page-state updates now persist session state before navigating and skip navigation when the browser has disconnected, avoiding an unhandled navigation failure. The navigation rail's overflow button also has consistent sizing, icon alignment, and hover styling in expanded and collapsed layouts and both light and dark themes. ([#20545](microsoft/aspire#20545), backport of [#20527](microsoft/aspire#20527), @JamesNK) - 🖥️ **Container exec watches could terminate shortly after AppHost startup** — A stalled DCP watch connection could produce a critical `Watch task over Kubernetes ContainerExec resources terminated unexpectedly` error and stop subsequent terminal state and log updates from being observed. Watch connection attempts now retry after timeouts, and periodic restarts correctly recreate connections without swallowing unrelated cancellation. Regression introduced in 13.6.0. ([#20664](microsoft/aspire#20664), backport of [#20466](microsoft/aspire#20466), @radical) - 🪟 **Session-scoped containers could remain running after stopping a .NET AppHost on Windows** — AppHosts launched through `dotnet run` or `dotnet watch` now allow DCP to finish resource cleanup during shutdown, including existing Ctrl+C and `aspire stop` flows. Persistent resources remain unaffected, while direct .NET launches and TypeScript/polyglot AppHosts retain their existing process protection. Fixes [#20495](microsoft/aspire#20495). ([#20514](microsoft/aspire#20514), backport of [#20494](microsoft/aspire#20494), @danegsta) --- *Full Changelog: [v13.6.0...v13.6.1](microsoft/aspire@v13.6.0...v13.6.1)* *Full commit: [3751e615ad660621f2a7aa4c390ef48e08a0eed8](microsoft/aspire@3751e615ad660621f2a7aa4c390ef48e08a0eed8)* Commits viewable in [compare view](https://github.com/microsoft/aspire/commits). </details> Updated [Aspire.Hosting.PostgreSQL](https://github.com/microsoft/aspire) from 13.6.0 to 13.6.3. <details> <summary>Release notes</summary> _Sourced from [Aspire.Hosting.PostgreSQL's releases](https://github.com/microsoft/aspire/releases)._ ## 13.6.2 *Full commit: [af07e33f8d1ef733645138b3f8e36067d073148d](microsoft/aspire@af07e33f8d1ef733645138b3f8e36067d073148d)* ## What's Changed * [release/13.6] Bump version to 13.6.2 by @danegsta with @Copilot in microsoft/aspire#20877 * [release/13.6] Pin MessagePack to 2.5.307 for security fixes by @eerhardt in microsoft/aspire#21156 **Full Changelog**: microsoft/aspire@v13.6.1...v13.6.2 ## 13.6.1 ## What's New in Aspire 13.6.1 Patch release for Aspire 13.6 that reduces dashboard CPU usage during sustained metric ingestion, restores scrolling in the Metrics tree, improves dashboard navigation, fixes container exec watch failures, and ensures session-scoped containers are cleaned up when stopping .NET AppHosts on Windows. ### 🐛 Fixes - 📊 **Dashboard CPU usage could increase during long-running metric ingestion** — Metric retention repeatedly scanned retained history on every insertion, causing steadily increasing CPU usage even with a fixed workload. Cleanup now skips dimensions below capacity and removes only the oldest surplus points when needed. Existing retention limits and exemplar behavior are unchanged, and no configuration changes are required. Regression introduced in 13.6. Fixes [#20725](microsoft/aspire#20725). ([#20747](microsoft/aspire#20747), backport of [#20736](microsoft/aspire#20736), @JamesNK) - 📈 **The Metrics tree could not be scrolled** — The meter and instrument tree now scrolls when it exceeds the viewport, allowing you to reach and select instruments below the fold. Regression introduced in 13.6. Fixes [#20728](microsoft/aspire#20728). ([#20762](microsoft/aspire#20762), backport of [#20758](microsoft/aspire#20758), @heyysiri) - 🧭 **Dashboard navigation could fail after a browser disconnect** — Pending page-state updates now persist session state before navigating and skip navigation when the browser has disconnected, avoiding an unhandled navigation failure. The navigation rail's overflow button also has consistent sizing, icon alignment, and hover styling in expanded and collapsed layouts and both light and dark themes. ([#20545](microsoft/aspire#20545), backport of [#20527](microsoft/aspire#20527), @JamesNK) - 🖥️ **Container exec watches could terminate shortly after AppHost startup** — A stalled DCP watch connection could produce a critical `Watch task over Kubernetes ContainerExec resources terminated unexpectedly` error and stop subsequent terminal state and log updates from being observed. Watch connection attempts now retry after timeouts, and periodic restarts correctly recreate connections without swallowing unrelated cancellation. Regression introduced in 13.6.0. ([#20664](microsoft/aspire#20664), backport of [#20466](microsoft/aspire#20466), @radical) - 🪟 **Session-scoped containers could remain running after stopping a .NET AppHost on Windows** — AppHosts launched through `dotnet run` or `dotnet watch` now allow DCP to finish resource cleanup during shutdown, including existing Ctrl+C and `aspire stop` flows. Persistent resources remain unaffected, while direct .NET launches and TypeScript/polyglot AppHosts retain their existing process protection. Fixes [#20495](microsoft/aspire#20495). ([#20514](microsoft/aspire#20514), backport of [#20494](microsoft/aspire#20494), @danegsta) --- *Full Changelog: [v13.6.0...v13.6.1](microsoft/aspire@v13.6.0...v13.6.1)* *Full commit: [3751e615ad660621f2a7aa4c390ef48e08a0eed8](microsoft/aspire@3751e615ad660621f2a7aa4c390ef48e08a0eed8)* Commits viewable in [compare view](https://github.com/microsoft/aspire/commits). </details> Updated [Aspire.Hosting.Testing](https://github.com/microsoft/aspire) from 13.6.0 to 13.6.3. <details> <summary>Release notes</summary> _Sourced from [Aspire.Hosting.Testing's releases](https://github.com/microsoft/aspire/releases)._ ## 13.6.2 *Full commit: [af07e33f8d1ef733645138b3f8e36067d073148d](microsoft/aspire@af07e33f8d1ef733645138b3f8e36067d073148d)* ## What's Changed * [release/13.6] Bump version to 13.6.2 by @danegsta with @Copilot in microsoft/aspire#20877 * [release/13.6] Pin MessagePack to 2.5.307 for security fixes by @eerhardt in microsoft/aspire#21156 **Full Changelog**: microsoft/aspire@v13.6.1...v13.6.2 ## 13.6.1 ## What's New in Aspire 13.6.1 Patch release for Aspire 13.6 that reduces dashboard CPU usage during sustained metric ingestion, restores scrolling in the Metrics tree, improves dashboard navigation, fixes container exec watch failures, and ensures session-scoped containers are cleaned up when stopping .NET AppHosts on Windows. ### 🐛 Fixes - 📊 **Dashboard CPU usage could increase during long-running metric ingestion** — Metric retention repeatedly scanned retained history on every insertion, causing steadily increasing CPU usage even with a fixed workload. Cleanup now skips dimensions below capacity and removes only the oldest surplus points when needed. Existing retention limits and exemplar behavior are unchanged, and no configuration changes are required. Regression introduced in 13.6. Fixes [#20725](microsoft/aspire#20725). ([#20747](microsoft/aspire#20747), backport of [#20736](microsoft/aspire#20736), @JamesNK) - 📈 **The Metrics tree could not be scrolled** — The meter and instrument tree now scrolls when it exceeds the viewport, allowing you to reach and select instruments below the fold. Regression introduced in 13.6. Fixes [#20728](microsoft/aspire#20728). ([#20762](microsoft/aspire#20762), backport of [#20758](microsoft/aspire#20758), @heyysiri) - 🧭 **Dashboard navigation could fail after a browser disconnect** — Pending page-state updates now persist session state before navigating and skip navigation when the browser has disconnected, avoiding an unhandled navigation failure. The navigation rail's overflow button also has consistent sizing, icon alignment, and hover styling in expanded and collapsed layouts and both light and dark themes. ([#20545](microsoft/aspire#20545), backport of [#20527](microsoft/aspire#20527), @JamesNK) - 🖥️ **Container exec watches could terminate shortly after AppHost startup** — A stalled DCP watch connection could produce a critical `Watch task over Kubernetes ContainerExec resources terminated unexpectedly` error and stop subsequent terminal state and log updates from being observed. Watch connection attempts now retry after timeouts, and periodic restarts correctly recreate connections without swallowing unrelated cancellation. Regression introduced in 13.6.0. ([#20664](microsoft/aspire#20664), backport of [#20466](microsoft/aspire#20466), @radical) - 🪟 **Session-scoped containers could remain running after stopping a .NET AppHost on Windows** — AppHosts launched through `dotnet run` or `dotnet watch` now allow DCP to finish resource cleanup during shutdown, including existing Ctrl+C and `aspire stop` flows. Persistent resources remain unaffected, while direct .NET launches and TypeScript/polyglot AppHosts retain their existing process protection. Fixes [#20495](microsoft/aspire#20495). ([#20514](microsoft/aspire#20514), backport of [#20494](microsoft/aspire#20494), @danegsta) --- *Full Changelog: [v13.6.0...v13.6.1](microsoft/aspire@v13.6.0...v13.6.1)* *Full commit: [3751e615ad660621f2a7aa4c390ef48e08a0eed8](microsoft/aspire@3751e615ad660621f2a7aa4c390ef48e08a0eed8)* Commits viewable in [compare view](https://github.com/microsoft/aspire/commits). </details> Updated [Aspire.Hosting.Valkey](https://github.com/microsoft/aspire) from 13.6.0 to 13.6.3. <details> <summary>Release notes</summary> _Sourced from [Aspire.Hosting.Valkey's releases](https://github.com/microsoft/aspire/releases)._ ## 13.6.2 *Full commit: [af07e33f8d1ef733645138b3f8e36067d073148d](microsoft/aspire@af07e33f8d1ef733645138b3f8e36067d073148d)* ## What's Changed * [release/13.6] Bump version to 13.6.2 by @danegsta with @Copilot in microsoft/aspire#20877 * [release/13.6] Pin MessagePack to 2.5.307 for security fixes by @eerhardt in microsoft/aspire#21156 **Full Changelog**: microsoft/aspire@v13.6.1...v13.6.2 ## 13.6.1 ## What's New in Aspire 13.6.1 Patch release for Aspire 13.6 that reduces dashboard CPU usage during sustained metric ingestion, restores scrolling in the Metrics tree, improves dashboard navigation, fixes container exec watch failures, and ensures session-scoped containers are cleaned up when stopping .NET AppHosts on Windows. ### 🐛 Fixes - 📊 **Dashboard CPU usage could increase during long-running metric ingestion** — Metric retention repeatedly scanned retained history on every insertion, causing steadily increasing CPU usage even with a fixed workload. Cleanup now skips dimensions below capacity and removes only the oldest surplus points when needed. Existing retention limits and exemplar behavior are unchanged, and no configuration changes are required. Regression introduced in 13.6. Fixes [#20725](microsoft/aspire#20725). ([#20747](microsoft/aspire#20747), backport of [#20736](microsoft/aspire#20736), @JamesNK) - 📈 **The Metrics tree could not be scrolled** — The meter and instrument tree now scrolls when it exceeds the viewport, allowing you to reach and select instruments below the fold. Regression introduced in 13.6. Fixes [#20728](microsoft/aspire#20728). ([#20762](microsoft/aspire#20762), backport of [#20758](microsoft/aspire#20758), @heyysiri) - 🧭 **Dashboard navigation could fail after a browser disconnect** — Pending page-state updates now persist session state before navigating and skip navigation when the browser has disconnected, avoiding an unhandled navigation failure. The navigation rail's overflow button also has consistent sizing, icon alignment, and hover styling in expanded and collapsed layouts and both light and dark themes. ([#20545](microsoft/aspire#20545), backport of [#20527](microsoft/aspire#20527), @JamesNK) - 🖥️ **Container exec watches could terminate shortly after AppHost startup** — A stalled DCP watch connection could produce a critical `Watch task over Kubernetes ContainerExec resources terminated unexpectedly` error and stop subsequent terminal state and log updates from being observed. Watch connection attempts now retry after timeouts, and periodic restarts correctly recreate connections without swallowing unrelated cancellation. Regression introduced in 13.6.0. ([#20664](microsoft/aspire#20664), backport of [#20466](microsoft/aspire#20466), @radical) - 🪟 **Session-scoped containers could remain running after stopping a .NET AppHost on Windows** — AppHosts launched through `dotnet run` or `dotnet watch` now allow DCP to finish resource cleanup during shutdown, including existing Ctrl+C and `aspire stop` flows. Persistent resources remain unaffected, while direct .NET launches and TypeScript/polyglot AppHosts retain their existing process protection. Fixes [#20495](microsoft/aspire#20495). ([#20514](microsoft/aspire#20514), backport of [#20494](microsoft/aspire#20494), @danegsta) --- *Full Changelog: [v13.6.0...v13.6.1](microsoft/aspire@v13.6.0...v13.6.1)* *Full commit: [3751e615ad660621f2a7aa4c390ef48e08a0eed8](microsoft/aspire@3751e615ad660621f2a7aa4c390ef48e08a0eed8)* Commits viewable in [compare view](https://github.com/microsoft/aspire/commits). </details> Pinned [Aspire.Npgsql.EntityFrameworkCore.PostgreSQL](https://github.com/microsoft/aspire) at 13.6.3. <details> <summary>Release notes</summary> _Sourced from [Aspire.Npgsql.EntityFrameworkCore.PostgreSQL's releases](https://github.com/microsoft/aspire/releases)._ ## 13.6.2 *Full commit: [af07e33f8d1ef733645138b3f8e36067d073148d](microsoft/aspire@af07e33f8d1ef733645138b3f8e36067d073148d)* ## What's Changed * [release/13.6] Bump version to 13.6.2 by @danegsta with @Copilot in microsoft/aspire#20877 * [release/13.6] Pin MessagePack to 2.5.307 for security fixes by @eerhardt in microsoft/aspire#21156 **Full Changelog**: microsoft/aspire@v13.6.1...v13.6.2 ## 13.6.1 ## What's New in Aspire 13.6.1 Patch release for Aspire 13.6 that reduces dashboard CPU usage during sustained metric ingestion, restores scrolling in the Metrics tree, improves dashboard navigation, fixes container exec watch failures, and ensures session-scoped containers are cleaned up when stopping .NET AppHosts on Windows. ### 🐛 Fixes - 📊 **Dashboard CPU usage could increase during long-running metric ingestion** — Metric retention repeatedly scanned retained history on every insertion, causing steadily increasing CPU usage even with a fixed workload. Cleanup now skips dimensions below capacity and removes only the oldest surplus points when needed. Existing retention limits and exemplar behavior are unchanged, and no configuration changes are required. Regression introduced in 13.6. Fixes [#20725](microsoft/aspire#20725). ([#20747](microsoft/aspire#20747), backport of [#20736](microsoft/aspire#20736), @JamesNK) - 📈 **The Metrics tree could not be scrolled** — The meter and instrument tree now scrolls when it exceeds the viewport, allowing you to reach and select instruments below the fold. Regression introduced in 13.6. Fixes [#20728](microsoft/aspire#20728). ([#20762](microsoft/aspire#20762), backport of [#20758](microsoft/aspire#20758), @heyysiri) - 🧭 **Dashboard navigation could fail after a browser disconnect** — Pending page-state updates now persist session state before navigating and skip navigation when the browser has disconnected, avoiding an unhandled navigation failure. The navigation rail's overflow button also has consistent sizing, icon alignment, and hover styling in expanded and collapsed layouts and both light and dark themes. ([#20545](microsoft/aspire#20545), backport of [#20527](microsoft/aspire#20527), @JamesNK) - 🖥️ **Container exec watches could terminate shortly after AppHost startup** — A stalled DCP watch connection could produce a critical `Watch task over Kubernetes ContainerExec resources terminated unexpectedly` error and stop subsequent terminal state and log updates from being observed. Watch connection attempts now retry after timeouts, and periodic restarts correctly recreate connections without swallowing unrelated cancellation. Regression introduced in 13.6.0. ([#20664](microsoft/aspire#20664), backport of [#20466](microsoft/aspire#20466), @radical) - 🪟 **Session-scoped containers could remain running after stopping a .NET AppHost on Windows** — AppHosts launched through `dotnet run` or `dotnet watch` now allow DCP to finish resource cleanup during shutdown, including existing Ctrl+C and `aspire stop` flows. Persistent resources remain unaffected, while direct .NET launches and TypeScript/polyglot AppHosts retain their existing process protection. Fixes [#20495](microsoft/aspire#20495). ([#20514](microsoft/aspire#20514), backport of [#20494](microsoft/aspire#20494), @danegsta) --- *Full Changelog: [v13.6.0...v13.6.1](microsoft/aspire@v13.6.0...v13.6.1)* *Full commit: [3751e615ad660621f2a7aa4c390ef48e08a0eed8](microsoft/aspire@3751e615ad660621f2a7aa4c390ef48e08a0eed8)* Commits viewable in [compare view](https://github.com/microsoft/aspire/commits). </details> Pinned [Aspire.StackExchange.Redis](https://github.com/microsoft/aspire) at 13.6.3. <details> <summary>Release notes</summary> _Sourced from [Aspire.StackExchange.Redis's releases](https://github.com/microsoft/aspire/releases)._ ## 13.6.2 *Full commit: [af07e33f8d1ef733645138b3f8e36067d073148d](microsoft/aspire@af07e33f8d1ef733645138b3f8e36067d073148d)* ## What's Changed * [release/13.6] Bump version to 13.6.2 by @danegsta with @Copilot in microsoft/aspire#20877 * [release/13.6] Pin MessagePack to 2.5.307 for security fixes by @eerhardt in microsoft/aspire#21156 **Full Changelog**: microsoft/aspire@v13.6.1...v13.6.2 ## 13.6.1 ## What's New in Aspire 13.6.1 Patch release for Aspire 13.6 that reduces dashboard CPU usage during sustained metric ingestion, restores scrolling in the Metrics tree, improves dashboard navigation, fixes container exec watch failures, and ensures session-scoped containers are cleaned up when stopping .NET AppHosts on Windows. ### 🐛 Fixes - 📊 **Dashboard CPU usage could increase during long-running metric ingestion** — Metric retention repeatedly scanned retained history on every insertion, causing steadily increasing CPU usage even with a fixed workload. Cleanup now skips dimensions below capacity and removes only the oldest surplus points when needed. Existing retention limits and exemplar behavior are unchanged, and no configuration changes are required. Regression introduced in 13.6. Fixes [#20725](microsoft/aspire#20725). ([#20747](microsoft/aspire#20747), backport of [#20736](microsoft/aspire#20736), @JamesNK) - 📈 **The Metrics tree could not be scrolled** — The meter and instrument tree now scrolls when it exceeds the viewport, allowing you to reach and select instruments below the fold. Regression introduced in 13.6. Fixes [#20728](microsoft/aspire#20728). ([#20762](microsoft/aspire#20762), backport of [#20758](microsoft/aspire#20758), @heyysiri) - 🧭 **Dashboard navigation could fail after a browser disconnect** — Pending page-state updates now persist session state before navigating and skip navigation when the browser has disconnected, avoiding an unhandled navigation failure. The navigation rail's overflow button also has consistent sizing, icon alignment, and hover styling in expanded and collapsed layouts and both light and dark themes. ([#20545](microsoft/aspire#20545), backport of [#20527](microsoft/aspire#20527), @JamesNK) - 🖥️ **Container exec watches could terminate shortly after AppHost startup** — A stalled DCP watch connection could produce a critical `Watch task over Kubernetes ContainerExec resources terminated unexpectedly` error and stop subsequent terminal state and log updates from being observed. Watch connection attempts now retry after timeouts, and periodic restarts correctly recreate connections without swallowing unrelated cancellation. Regression introduced in 13.6.0. ([#20664](microsoft/aspire#20664), backport of [#20466](microsoft/aspire#20466), @radical) - 🪟 **Session-scoped containers could remain running after stopping a .NET AppHost on Windows** — AppHosts launched through `dotnet run` or `dotnet watch` now allow DCP to finish resource cleanup during shutdown, including existing Ctrl+C and `aspire stop` flows. Persistent resources remain unaffected, while direct .NET launches and TypeScript/polyglot AppHosts retain their existing process protection. Fixes [#20495](microsoft/aspire#20495). ([#20514](microsoft/aspire#20514), backport of [#20494](microsoft/aspire#20494), @danegsta) --- *Full Changelog: [v13.6.0...v13.6.1](microsoft/aspire@v13.6.0...v13.6.1)* *Full commit: [3751e615ad660621f2a7aa4c390ef48e08a0eed8](microsoft/aspire@3751e615ad660621f2a7aa4c390ef48e08a0eed8)* Commits viewable in [compare view](https://github.com/microsoft/aspire/commits). </details> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Backport of #20758 to release/13.6
/cc James Newton-King (@JamesNK) Siri (@heyysiri)
Customer Impact
In Aspire 13.6, the Metrics page's meter/instrument tree cannot be scrolled when it exceeds the viewport, preventing customers from reaching and selecting metrics below the fold.
Testing
Manually verified in Brave that the pane does not scroll before the change and that mouse-wheel scrolling reveals lower meters after the change. No automated test was added because existing dashboard tests do not validate visual layout.
Risk
Low. This is a localized CSS change that applies the chart pane's existing
overflow: autobehavior to the metrics tree pane.Regression?
Yes — introduced by the Fluent UI Blazor v5 migration in #19431.