.NET: fix: filter filesystem checkpoint index by session#6132
Conversation
fc2cb82 to
665462f
Compare
|
Updated in 04e1cba to include the parent filter as well. The filesystem index now persists the parent checkpoint id, reloads it with the index, and applies withParent in RetrieveIndexAsync. I also added coverage for both the live store and a reopened store so the persisted index path is covered. Validation:
Note: this machine has only .NET SDK 10.0.203, so direct dotnet test hits the Microsoft.Testing.Platform/VSTest entrypoint error. I ran the generated MTP test app directly after build. |
334acbe to
9bf2a5b
Compare
|
Rebased this branch onto current Validation on Windows: |
9bf2a5b to
576da57
Compare
|
Rebased onto the latest Validation:
|
576da57 to
c681aa3
Compare
|
Rebased onto the latest The requested Current local check against fetched Validation on Windows: |
c681aa3 to
fae6a63
Compare
|
Rebased onto current Validation on Windows: |
fae6a63 to
a864656
Compare
|
Rebased onto current Validation on Windows: |
|
I checked this review point again. The current branch now filters
Re-ran focused validation:
|
|
Addressed the legacy-index compatibility concern in f273e0e. New index rows now explicitly record whether parent metadata is known, which distinguishes a known root checkpoint from a pre-upgrade row whose parent is unknown. Parent-filtered lookup keeps unknown legacy rows discoverable instead of silently dropping them, while new rows still filter exactly. Added a reopened-store legacy-index regression test. Validation: dotnet build succeeded with 0 warnings/errors; FileSystemJsonCheckpointStoreTests 9 passed; dotnet format --verify-no-changes passed (workspace-load warning only); git diff --check passed. |
f273e0e to
941d9e5
Compare
|
Updated in I added a reopened legacy-index regression test that calls Validation on Windows: |
941d9e5 to
bd4dde3
Compare
|
Rebased onto current The remaining review case is still covered by the new legacy-index test. Validation after the rebase: |
Summary
Fixes #5942.
To verify
Note: direct dotnet test is blocked locally by the Microsoft.Testing.Platform / .NET 10 VSTest entrypoint error, so I ran the generated test runner executable instead.