Repository navigation
fix: preserve persistent lab grant lookup errors - #44
Merged
Horcag merged 2 commits intoOct 26, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A provider or enrollment lookup failure while revalidating a matching persistent VM grant could be discarded and later appear as a generic
approval_requireddenial. Preserve the lookup cause and block dispatch; the same stored grant remains usable after recovery. Invalid, revoked, inactive, foreign, and replaced-enrollment grants remain excluded, with the existing grant lease and enrollment fence intact.The test-only retirement fixture now has a 90-second budget for PowerShell startup and compilation. A private temporary stage file adds bounded stage, elapsed-time and
ctx.Err()diagnostics while preservingCombinedOutput, strict JSON checks and malformed-frame sentinels. The original Windows CI failure recorded 30.02 seconds and exit 1 without measuring the stalled stage. A standalone cold-process baseline with the original 30-second limit and the instrumented candidate both passed the exact native case without skips on Windows LTSC with PowerShell 7.6.9; the original CI stall was not reproduced there.This is stacked on #36 (
perf/vm-operation-throughput).Validation: