-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
fix: preserve fallback models for future tasks #9054
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
Soulter
merged 2 commits into
AstrBotDevs:master
from
catDforD:fix/8996-future-task-fallback
Jun 27, 2026
+69
−3
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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
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
Oops, something went wrong.
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.
suggestion (testing): Consider adding a complementary test for when
provider_settingsis missing orNoneto cover the default behavior.This only exercises the case where
provider_settingsis present. Please add a test wherectx.get_config.return_valueeither omitsprovider_settingsor sets it toNone, and assert thatMainAgentBuildConfig.tool_call_timeoutfalls back to120and thatprovider_settingsbecomes an empty dict (or whatever the expected behavior is). That will protect against regressions in handling misconfigured or legacy configs.Suggested implementation:
The above changes assume that:
cron_manager._get_main_agent_build_config()that returns aMainAgentBuildConfigobject.MainAgentBuildConfigexposesprovider_settingsandtool_call_timeoutattributes, and the defaulttool_call_timeoutis120.If your cron manager uses a different method name or return type:
_get_main_agent_build_config()with the actual method that constructs the main agent build config for the active agent job.provider_settings,tool_call_timeout) to match the realMainAgentBuildConfig(or equivalent) API.120to keep the test aligned with configuration defaults.