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.
chore: retire the DEEPSEEK_YOLO env alias (#5443) #5841
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
Uh oh!
There was an error while loading. Please reload this page.
chore: retire the DEEPSEEK_YOLO env alias (#5443) #5841
Changes from all commits
949a00eFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
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.
[WARNING] TUI yolo alias test reuses mutated Config, second scenario not isolated
The test creates one
configand mutates it with the firstapply_env_overrides, leavingconfig.yolo = Some(true). The second scenario removesCODEWHALE_YOLOand setsDEEPSEEK_YOLO, but if the alias were not read,apply_env_overrideswould not overwrite the existingconfig.yolo, so the assertion would still pass. This makes the test unable to catch regressions whereDEEPSEEK_YOLOis no longer honored. ResetconfigtoConfig::default()before the second scenario (or use a freshConfig).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.
Reset config before testing the deprecated alias so the assertion does not pass because of state left by the previous case.
Uh oh!
There was an error while loading. Please reload this page.