fix: remove redundant message cleaning logic in callModelWithLogging

The previous message cleaning logic was flawed:
- cleanedMsg.Content was already set to message.Content
- The condition checked if message.Content == "" then set cleanedMsg.Content = ""
- This was redundant since cleanedMsg.Content would already be empty

The real fix for the API 400 error is in planner.go where we ensure Tool messages
have non-empty content. The utils.go changes were unnecessary.
This commit is contained in:
lilong.129
2025-06-26 13:16:12 +08:00
parent e070801b00
commit 90ce090e35
4 changed files with 5 additions and 27 deletions

View File

@@ -1 +1 @@
v5.0.0-beta-2506261057
v5.0.0-beta-2506261341