First 1 or 2 tool calls succeed with Ollama, subsequent tool calls fail with exposed <tool_call> in assistant response

[dto]

Instead of the correct Emacs Lisp functions being invoked by llm, after a few tries I start to get stuff like this in the assistant message instead of as a proper tool call:

<tool_call>
{"name": "systemName", "arguments": null}
</tool_call>

Seems to happen no matter which tools enabled model i use.

[ahyatt]

It certainly possible that this is a bug of some sort. Is this in a conversation (using the same prompt over and over) or with separate prompts?

[dto]

This is in a conversation. I can provide more debug info, I'll make another post on this thread.

[dto]

I'm reading up here on the Qwen model I'm using: https://qwen.readthedocs.io/en/latest/framework/function_call.html where it says "As before, chances are that there are corner cases where tool calls are generated but they are malformed and cannot be parsed. For production code, we should try parsing by ourselves." Which I am doing now, to catch tool calls that aren't caught by Emacs and/or Ollama. I think the error may be on the Ollama side because the role:assistant is set already when Emacs gets the response (I think)

[ahyatt]

Multiple conversational rounds with function calling is always a bit tricky because every provider has their own pecularities with it. I'll look into this in the next few days.

[dto]

Thank you! I'll keep my eyes peeled, and i'll keep trying to debug. Might have to put some print statements into PLZ

…

On Sun, Nov 3, 2024 at 11:49 PM Andrew Hyatt ***@***.***> wrote: Multiple conversational rounds with function calling is always a bit tricky because every provider has their own pecularities with it. I'll look into this in the next few days. — Reply to this email directly, view it on GitHub <#94 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAFSI4N6RO7DVBRL4EO4LDZ63VGFAVCNFSM6AAAAABRBQVNWKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMJTHA2TIOA> . You are receiving this because you authored the thread.Message ID: ***@***.***>