gemini-cli - 💡(How to fix) Fix Please ensure that function call turn comes immediately after a user turn or after a function response turn. [1 comments, 2 participants]

TL;DR

The issue is likely due to incorrect turn ordering in the Gemini API requests, and reordering the turns may resolve the issue.

Guidance

• Verify that the function call turn is indeed being sent immediately after a user turn or a function response turn, as the error message suggests.
• Review the Gemini API documentation to ensure that the turn ordering is correct and follows the expected sequence.
• Check the client code to see if there are any asynchronous or concurrent requests that may be causing the turns to be sent out of order.
• Consider adding logging or debugging statements to track the order of turns being sent to the Gemini API.

Notes

The exact solution may depend on the specific implementation and usage of the Gemini API, which is not fully described in the issue.

Recommendation

Apply workaround: Reorder the turns to ensure that function call turns come immediately after user turns or function response turns, as this is the most likely cause of the issue and is explicitly stated in the error message.