Spaces:
Running
"Error while parsing tool calls, please retry"
I keep getting "Error while parsing tool calls, please retry" which marks the response as "Retry" only, meaning I can't write a reply, only "retry", even though it's a perfectly valid response and I do not use tools. Sometimes this happens as often as on 90% of responses. This is extremely annoying, please fix.
I mostly use the newest "meta-llama/Meta-Llama-3.1-70B-Instruct" but it happened on 3.0 as well, and I think on other models as well.
Could you share a conversation where this happens ?
I'll see if I can get a repro. It's not doing it right now. It might be related to "Model is overloaded".
Hello, I have the same problem, and sometime just at the start of the conversation with the "meta-llama/Meta-Llama-3.1-70B-Instruct" model.
After that, I can't write anything.
(In any languages)
I'm still getting the error. I have not been able to reproduce it in a conversation I can share, but I also didn't try very hard. It only seems to happen with the meta-llama/Meta-Llama-3.1-70B-Instruct model.
It also seems like "tools" are polluting the prompts, and since I don't want or use tools, this is something I didn't ask for and don't want. Several times unwanted JSON and undesired technical speech starts seeping into the responses, for example I got this as a complete response (content rewritten):
{"tool_name": "directlyAnswer", "parameters": {"query": "My prompt rewritten", "transkripsjon": "A start of the response cut off after 4 words"}}
@Ezriel if you disable all tools in the tool selector we will bypass the tool step entirely and this shouldn't affect your prompts then, let me know if that helps!
If you get a reproduction you can share, especially for the last one where the model gives you a JSON answer when you didn't want it to, that would be great.
I think I didn't get this in a while, especially if it bypasses the tool step entirely like you said, so I'm going to close this. Thanks!
I got this same error message with the same symptoms with 0 tools twice now, so it looks like this is still not solved.