fix: 修复 Deepseek API 消息格式兼容性问题

[chenhuping]

• 合并连续的用户消息（user role）为单条消息
• 确保符合 Deepseek API 的消息顺序要求

当消息队列中出现多个连续的 user role 消息时，Deepseek API 会返回 400 Bad Request 错误，具体报错如下：

Summary by CodeRabbit

• Refactor
  • Streamlined summary messaging by consolidating previously separate components into one unified block. This enhancement offers a cleaner, more organized presentation and improves readability for end users.

[coderabbitai]

Walkthrough

The change consolidates two separate message entries in the process_summary function into one. Instead of creating separate list items for FINAL_SUMMARY_PROMPT and final_summaries_content, it now constructs a single string that includes both, separated by two newline characters. This revised message is then passed to the generate_diff_summary function, streamlining the message handling process.

Changes

File	Change Summary
review_engine/handler/.../default_handler.py	Consolidated two entries into one in the process_summary function to combine FINAL_SUMMARY_PROMPT and final summaries

Sequence Diagram(s)

sequenceDiagram
    participant Handler as process_summary
    participant Diff as generate_diff_summary
    Handler->>Handler: Combine FINAL_SUMMARY_PROMPT and final_summaries_content (separated by newlines)
    Handler->>Diff: Send consolidated summary message

Loading

Poem

In a code burrow, I happily hop,
Merging words as the lines do stop.
With a twitch of my nose and a digital kiss,
One message flows—simplicity, bliss!
CodeRabbit cheers with a whiskered delight!
🥕🐇

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f6a03a9 and b0169f8.

📒 Files selected for processing (1)

• review_engine/handler/default_handler.py (1 hunks)

🔇 Additional comments (1)

review_engine/handler/default_handler.py (1)

94-94: LGTM! Fix successfully addresses the Deepseek API message format compatibility issue.

This change correctly implements the merging of consecutive user messages into a single message with appropriate formatting, which aligns with the PR objective. The use of \n\n separator maintains clear distinction between the prompt and content while ensuring proper message format for the Deepseek API.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[skrcoder]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Message Formatting Verify that combining the final summary prompt and content into a single message maintains all necessary information and formatting for the Deepseek API. "content": f"{FINAL_SUMMARY_PROMPT}\n\n{final_summaries_content}"