-
Notifications
You must be signed in to change notification settings - Fork 14.2k
fix(patch): cherry-pick 68afb72 to release/v0.12.0-preview.3-pr-12306 to patch version v0.12.0-preview.3 and create version 0.12.0-preview.4 #12327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
mattKorwel
merged 1 commit into
release/v0.12.0-preview.3-pr-12306
from
hotfix/v0.12.0-preview.3/0.12.0-preview.4/preview/cherry-pick-68afb72/pr-12306
Oct 30, 2025
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changing the default compression threshold from
0.7to0.2breaks an existing unit test. The test case'should return NOOP if under token threshold and not forced'inpackages/core/src/services/chatCompressionService.test.tsis hardcoded to expect the old threshold.Specifically, the test mocks
getLastPromptTokenCountto return600andtokenLimitto return1000. The test comment even states:// Threshold is 0.7 * 1000 = 700. 600 < 700, so NOOP.With the new default of
0.2, the threshold becomes200, and600is no longer less than the threshold, causing the test to fail. The associated test file needs to be updated to reflect this new default value.