Skip to content

[Dashboard] Prune incompatible-schema run directories #19775

Description

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

DashboardRunStore.LoadRuns excludes metadata whose schema version differs from the current version. PruneRuns only iterates the successfully loaded _runs snapshot.

After a Dashboard schema upgrade, older-schema run directories become invisible to both selection and retention, so storage can grow beyond the advertised run limit.

Expected Behavior

Incompatible historical runs should remain non-selectable but still participate in retention cleanup.

Steps To Reproduce

  1. Create Run history with one Dashboard schema version.
  2. Start a Dashboard whose schema version has advanced.
  3. Create enough new runs to trigger retention.
  4. The old-schema directories are never selected as pruning candidates.

Exceptions (if any)

N/A

Aspire doctor output

Aspire CLI 13.6.0-pr.18924.g5ee63941
Windows 10.0.26200 and Ubuntu 24.04.3

Anything else?

Related to #18924. Source: src/Aspire.Dashboard/ServiceClient/DashboardRunStore.cs:336-369,440-465. This was mentioned during PR review and remains on current main.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions