👀 @junity233

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。 请确保您已经提供了尽可能多的背景信息。

Hey @junity233! 👋 I'm here to help you with any bugs, questions, or contributions you have. Let's squash this bug together!

The error you're encountering with Deepseeker R1 is due to the requirement that the first message, after any system message, must be a user message. The error message indicates that an assistant message was detected instead. This suggests that the message sequence is not being correctly managed, leading to an invalid request.

To resolve this issue, ensure that the message sequence starts with a user message after any system message. You might need to adjust the logic in your application to enforce this sequence, especially when handling multiple rounds of conversation. This could involve checking the role of the first message in each conversation round and ensuring it is set to 'user' before sending it to Deepseeker R1.

To continue talking to Dosu, mention @dosu.

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

Here is a picture:

✅ @junity233

This issue is closed, If you have any questions, you can comment and reply.
此问题已经关闭。如果您有任何问题，可以留言并回复。

🎉 This issue has been resolved in version 1.49.7 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀