Error handling model response

[badStephane]

Before submitting your bug report

• I've tried using the "Ask AI" feature on the Continue docs site to see if the docs have an answer
• I'm not able to find a related conversation on GitHub discussions that reports the same bug
• I'm not able to find an open issue that reports the same bug
• I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

- OS:
- Continue version:
- IDE version:
- Model:
- config:
  

  
  OR link to agent in Continue hub:

Description

There was an error handling the response from deepseek-r1:latest.

Please try to submit your message again, and if the error persists, let us know by reporting the issue using the buttons below.

To reproduce

select deepseek-r1 model and launch a prompt

Log output

request to http://127.0.0.1:11434/api/chat failed, reason: socket hang up

[uinstinct]

I assume you are using ollama. Are you able to chat with the model using ollama run deepseek-r1?

[mwichmann]

I'm seeing the same basic error message (lots) on complex things with lots of thinking. Timeout perhaps? ollama and gpt-oss in this particular instance. Sorry, don't have a reproducer. The output of one of these looked like:

Thus answer.', err=invalid character 'a' looking for beginning of value {"error":"error parsing tool call: raw='assistant couldn't find the tool. The tool might be called \"assistant\" but maybe the name is different. In previous problems, the tool name for reading file is \"assistant\". But here it's failing. There might be a tool named \"assistant\" but it expects JSON with a \"file\" field. However, the tool name itself may be \"assistant\". But the error says \"Tool assistant not found\". That means tool name is wrong.\n\nMaybe the correct tool is \"assistant\" but we need to pass \"assistant_file\" or \"assistant_reader\". I'm not sure.\n\nLet's see if there is a tool \"assistant\" in the system. In these tasks, we often have a \"assistant\" tool to read file? Actually the tool is typically named \"assistant\" in the earlier example we used \"assistant\" to read file. But it's not found.\n\nWe could attempt to use \"assistant\" with the correct name \"assistant\" but the environment doesn't have it. Possibly the tool name is \"assistant_file\". Let's guess.\n\nTry with \"assistant_file\" tool.assistant failed because the arguments were invalid, with the following message: Tool assistant_file not found\n\nWe need a different approach: We can ask the system for a list of available tools. There's no tool for that. Perhaps we can introspect by reading the .env? There's no.\n\nWe might have to proceed without reading the file, but we need to answer the question. The user wants to know if there's an error in scons_title.xsl referencing the three elements: margin-left, margin-right, and column-width.\n\nWe can try to inspect the file manually? But we can't read it. But maybe we can approximate. The user says scons_title.xsl references all three elements being complained about. They suspect it's error. So answer: It likely uses empty values or missing attributes. We can propose modifications.\n\nWe need to explain underlying cause: The FO file is generated by the XSL transformation. The error indicates that the XSL is generating an empty margin-left/right attribute. The underlying cause is likely that the XSL uses a value from a variable that is empty or not set. The empty value arises because the variable is empty. Similarly, the column-width uses proportional-column-width but the table is not set to fixed layout.\n\nTherefore the answer: In scons_title.xsl, there is a template for the fo:page-sequence with margin-left/right set from variables that might not be defined, causing empty values. And there's a table where column-width uses proportional-column-width but table-layout not fixed. The fix is to either set defaults for those attributes, or ensure that table-layout fixed is set when using proportional-column-width. Alternatively, modify the XSL to use static values or wrap in conditional.\n\nWe can propose to patch scons_title.xsl: Add default values for margin-left/right (e.g., \"1in\") and modify the table template to set table-layout=\"fixed\" if proportional-column-width is used.\n\nWe can't edit the file directly here, but we can propose the diff.\n\nThus answer.', err=invalid character 'a' looking for beginning of value"}:

[uinstinct]

Can you give it a try with some other model like llama 3 and see if it works fine?

[badStephane]

Thanks for your contribution I'm going to try it and tell you back

[badStephane]

It works but I can't use it for edit file in vscode

[uinstinct]

what is the error that you are seeing when it edits a file?
are you using agent or edit mode?