Skip to content

fix(conversation): unify provider/model resolution across send/cron paths (ELECTRON-1HX, ELECTRON-1HM)#326

Open
TCP404 wants to merge 1 commit into
mainfrom
boii/fix-electron-1hx
Open

fix(conversation): unify provider/model resolution across send/cron paths (ELECTRON-1HX, ELECTRON-1HM)#326
TCP404 wants to merge 1 commit into
mainfrom
boii/fix-electron-1hx

Conversation

@TCP404
Copy link
Copy Markdown
Collaborator

@TCP404 TCP404 commented May 25, 2026

Summary

  • Fix Sentry ELECTRON-1HX / ELECTRON-1HM: interactive send_message and the cron JobExecutor each had their own provider/model resolver. For some conversation row states the cron path produced a different provider/model than the user-facing path, leading to panics or surfaced errors.
  • Extract crates/aionui-conversation/src/task_options.rs (195 new lines) exposing provider_model_from_conversation_row(), used by both call sites.
  • Add 7 unit tests covering combinations of conversation row configurations.

Test plan

  • cargo test -p aionui-conversation
  • cargo test -p aionui-cron
  • just build -f
  • Manual: trigger a cron run on the same conversation and confirm provider/model match the interactive path.

Generated with Claude Code

…aths (ELECTRON-1HX, ELECTRON-1HM)

Extract provider_model_from_conversation_row() so interactive send_message
and cron JobExecutor share one resolver, preventing cron jobs from
picking up provider/model values that diverge from the conversation row.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@TCP404 TCP404 changed the title fix(conversation): 统一交互/cron 路径的 provider/model 解析 (ELECTRON-1HX, ELECTRON-1HM) fix(conversation): unify provider/model resolution across send/cron paths (ELECTRON-1HX, ELECTRON-1HM) May 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant