Repository navigation
Conversation
Quest-Claim: f40a083818d6b016
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.
Result
Released without implementation because moq-dev/moq#7328, head f191195, already contains the exact JS deferred newest-group floor fix, unresolved-track tests, and deletion of quest/m1/js-early-latest.md. Its active branch is quest/m2/pipeline-requests/subscribe. Recommend completing the quest through that existing PR, without duplicating or taking over its work.
Overlap
Validation
Temporarily applied the existing unresolved-track tests from the pipeline PR to current main. All three lite-01/03/05 cases failed: expected first served group 2, received 0. Applying only that PR existing JS publisher patch made all three pass (6 assertions). Removed both temporary patches afterward; the source checkout is clean. Full checks and a new review were unnecessary because no implementation is being published. The narrow reproduction ran directly after cancelling a load-gated attempt that had not started.
Impact
No public API or wire change. No implementation changes in this claim.
(Written by GPT-6.1 Sol)