Repository navigation
Conversation
Count queued assets before starting the post-configuration startup phase while preserving existing loading order, network throttling, retries, and deferred loading. Add an internal queue-computed hook and a CoreCLR test asset guard for stable phase totals, including a regression test for the guard. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Preserve upstream callback migration and readiness checks alongside startup queue accounting and its test guard. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
This was referenced Oct 11, 2026
This branch has not been deployed
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.
Queue and count CoreCLR browser startup resources upfront so download progress reports a stable total after configuration initializers finish. Preserve existing loading order, network throttling, retries, and deferred loading.
Initializers still run first because they can change resource selection; their progress and later lazy loads can increase the total. HTTP-cache-only prefetch is unchanged, and download-into-memory and subsequent create phases are counted separately.
Add an internal queue-computed hook and a CoreCLR test asset guard that checks stable totals and completion, with a regression test verifying the guard detects unexpected growth.
Note
This PR description was generated with the assistance of GitHub Copilot.