-
Notifications
You must be signed in to change notification settings - Fork 1.1k
fix(compaction): filter empty text parts to avoid API 400 #2395
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
Open
rastinder
wants to merge
1
commit into
MoonshotAI:main
Choose a base branch
from
rastinder:fix-compaction-empty-text-parts
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+9
−1
Open
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
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.
🔴 Defensive empty-content check is always True and never triggers
The defensive check at lines 192-196 is meant to skip compaction when all actual message content is empty (to avoid an API 400 error). However, it checks whether any
TextPartincompact_message.contenthas non-empty.strip()— and this will always beTruebecausecompact_message.contentalways contains:TextPart(text="## Message 1\nRole: user\nContent:\n")(appended at line 175 for every message into_compact, which is guaranteed non-empty by the check at line 167)TextPart(text="\n" + prompts.COMPACT)(appended at line 189, whereprompts.COMPACTis a ~73-line markdown document persrc/kimi_cli/prompts/compact.md)Both of these always pass the
p.text.strip()test, sonot any(...)is alwaysFalse, and the early return on line 196 is dead code. The exact edge case this was supposed to guard against (messages whose content is all empty/whitespaceTextParts or entirely non-text parts) will still send them to the API and trigger the 400 error.The check should exclude header and prompt parts
The comment says "no non-empty text parts besides headers and the prompt" but the code doesn't actually exclude headers and the prompt from the check. A correct implementation would track whether any actual content parts were added, e.g. with a counter or flag in the loop at lines 173-180.
Prompt for agents
Was this helpful? React with 👍 or 👎 to provide feedback.