Skip to content

"content.parts is not iterable" when interacting with Gemini 2.5 pro 05-06 model. #5776

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
3 tasks
cristianjs19 opened this issue May 21, 2025 · 1 comment
Open
3 tasks
Assignees
Labels
area:chat Relates to chat interface ide:vscode Relates specifically to VS Code extension kind:bug Indicates an unexpected problem or unintended behavior

Comments

@cristianjs19
Copy link

Before submitting your bug report

Relevant environment info

- OS: Linux Mint 20.3
- Continue version: 1.0.10
- IDE version: VSCode 1.99.3
- Model: Gemini 2.5 pro 05-06

Description

Image

I receive this error most of the times I send a question to this model Gemini 2.5 pro 05-06.

Is the only model with that I see the error. The other ones are working fine.

To reproduce

No response

Log output

Error handling webview message: {
  "msg": {
    "messageId": "c250e536-099b-4e32-b456-781dd140782c",
    "messageType": "llm/streamChat",
    "data": {
      "completionOptions": {},
      "title": "Gemini 2.5 pro 05-06",
      "messages": [
        {
          "role": "system",
          "content": "<important_rules>\n  Always include the language and file name in the info string when you write code blocks. \n  If you are editing \"src/main.py\" for example, your code block should start with ' src/main.py'\n\n  When addressing code modification requests, present a concise code snippet that\n  emphasizes only the necessary changes and uses abbreviated placeholders for\n  unmodified sections. For example:\n\n   /path/to/file\n  // ... rest of code here ...\n\n  {{ modified code here }}\n\n  // ... rest of code here ...\n\n  {{ another modification }}\n\n  // ... rest of code here ...\n  \n\n  In existing files, you should always restate the function or class that the snippet belongs to:\n\n   /path/to/file\n  // ... rest of code here ...\n  \n  function exampleFunction() {\n    // ... rest of code here ...\n    \n    {{ modified code here }}\n    \n    // ... rest of code here ...\n  }\n  \n  // ... rest of code here ...\n  \n\n  Since users have access to their complete file, they prefer reading only the\n  relevant modifications. It's perfectly acceptable to omit unmodified portions\n  at the beginning, middle, or end of files using these \"lazy\" comments. Only\n  provide the complete file when explicitly requested. Include a concise explanation\n  of changes unless the user specifically asks for code only.\n</important_rules>\n\nYou are an expert software developer. You give helpful and concise responses. You always try to bring brief responses, except when details or explanations are necessary and relevant."
        },
        
        // a few more messages there..

        {
          "role": "user",
          "content": [
            {
              "type": "text",
              "text": "\n\n api/session_recordings/urls.py (1-11)\nfrom rest_framework.routers import DefaultRouter\nfrom django.urls import path\nfrom .views import SessionViewSet, TrackingView, DashboardViewSet\n\nrouter = DefaultRouter()\nrouter.register(r'sessions', SessionViewSet)\nrouter.register(r'dashboard', DashboardViewSet, basename='dashboard')\n\nurlpatterns = [\n    path('track/', TrackingView.as_view(), name='tracking'),\n] + router.urls\n\nThere is a secong issue I need to solve there. I seeing this warning log in my server logs:\n[2025-05-21 15:01:57] WARNING [django.request:241] Not Found: /api/track/\n[2025-05-21 15:01:58] WARNING [django.request:241] Not Found: /api/track/\nHowever the sessions are being tracked, and it seems that the function it's actually called.\nWhen I check the network section in the devtools I see status 200 and all working fine:\nRequest URL\nhttps://api.replay-ui.app/api/track/\nRequest Method\nPOST\nStatus Code\n200 OK\nWhy I see these warning logs?\nWhat could be happening there?"
            }
          ]
        },
        {
          "role": "assistant",
          "content": ""
        }
      ]
    }
  }
}

TypeError: content.parts is not iterable
@dosubot dosubot bot added area:chat Relates to chat interface ide:vscode Relates specifically to VS Code extension kind:bug Indicates an unexpected problem or unintended behavior labels May 21, 2025
@mattparlane
Copy link

Also seeing this on Windows, same versions of Continue and Gemini, VS Code 1.100.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:chat Relates to chat interface ide:vscode Relates specifically to VS Code extension kind:bug Indicates an unexpected problem or unintended behavior
Projects
Status: Todo
Development

No branches or pull requests

3 participants