github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-08 08:59:13 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #15445] Gemma4.go: tool call parsing failed invalid character 'c' after object key #35630

New Issue
Open
opened 2026-04-22 20:17:03 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-22 20:17:03 -05:00
Owner
Copy Link

Originally created by @acwind on GitHub (Apr 9, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/15445

What is the issue?

Gemma4:26b - In the OpenClaw environment, when I use the blog skill to publish an article on GitHub Pages, the Ollama backend logs show an error. Looking at the logs, it appears to be a parsing failure during Tool Call execution.
The same skill works without any issues in other models.

Relevant log output

time=2026-04-09T14:52:01.555+08:00 level=WARN source=gemma4.go:299 msg="gemma4 tool call parsing failed" error="invalid character 'c' after object key:value pair\nrepair failed to produce valid JSON arguments" content="call:exec{command:<|\"|>mkdir -p /Users/coco/.openclaw/workspace/acwind.github.io/_posts/2026/04 && cp /Users/coco/.openclaw/workspace/articles/the-last-quiet-thing.md /Users/coco/.openclaw/workspace/acwind.github.io/_posts/2026/04/2026-04-09-the-last-quiet-thing.md && sed -i '' '1s/^/---\\ntitle: \"The Last Quiet Thing\"\\ncategories:\\n - 科技思考\\ntags: []\\nkey: the-last-quiet-thing\\n---\\n/' /Users/coco/.openclaw/workspace/acwind.github.io/_posts/202# No output from command, likely successful.\n<|channel>thought\n<channel|><|tool_call>call:exec{command:<|\"|>cd /Users/coco/.openclaw/workspace/acwind.github.io && git add _posts/2026/04/2026-04-09-the-last-quiet-thing.md && git commit -m \"新增博客：The Last Quiet Thing\" && git push origin main<|\"|>}"

OS

Windows

GPU

Nvidia

CPU

Intel, AMD

Ollama version

0.20.4

Originally created by @acwind on GitHub (Apr 9, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/15445 ### What is the issue? Gemma4:26b - In the OpenClaw environment, when I use the blog skill to publish an article on GitHub Pages, the Ollama backend logs show an error. Looking at the logs, it appears to be a parsing failure during Tool Call execution. The same skill works without any issues in other models. ### Relevant log output ```shell time=2026-04-09T14:52:01.555+08:00 level=WARN source=gemma4.go:299 msg="gemma4 tool call parsing failed" error="invalid character 'c' after object key:value pair\nrepair failed to produce valid JSON arguments" content="call:exec{command:<|\"|>mkdir -p /Users/coco/.openclaw/workspace/acwind.github.io/_posts/2026/04 && cp /Users/coco/.openclaw/workspace/articles/the-last-quiet-thing.md /Users/coco/.openclaw/workspace/acwind.github.io/_posts/2026/04/2026-04-09-the-last-quiet-thing.md && sed -i '' '1s/^/---\\ntitle: \"The Last Quiet Thing\"\\ncategories:\\n - 科技思考\\ntags: []\\nkey: the-last-quiet-thing\\n---\\n/' /Users/coco/.openclaw/workspace/acwind.github.io/_posts/202# No output from command, likely successful.\n<|channel>thought\n<channel|><|tool_call>call:exec{command:<|\"|>cd /Users/coco/.openclaw/workspace/acwind.github.io && git add _posts/2026/04/2026-04-09-the-last-quiet-thing.md && git commit -m \"新增博客：The Last Quiet Thing\" && git push origin main<|\"|>}" ``` ### OS Windows ### GPU Nvidia ### CPU Intel, AMD ### Ollama version 0.20.4
GiteaMirror added the bug label 2026-04-22 20:17:03 -05:00
GiteaMirror commented 2026-04-22 20:17:04 -05:00
Author
Owner
Copy Link

@drifkin commented on GitHub (Apr 9, 2026):

thanks for reporting. Unfortunately it looks like the tool call itself is invalid, it stops partway through the first call to think and then emits another tool call. We're looking into what's causing these kinds of malformed calls, thank you very much for the logs

<!-- gh-comment-id:4217838683 --> @drifkin commented on GitHub (Apr 9, 2026): thanks for reporting. Unfortunately it looks like the tool call itself is invalid, it stops partway through the first call to think and then emits another tool call. We're looking into what's causing these kinds of malformed calls, thank you very much for the logs
GiteaMirror commented 2026-04-22 20:17:05 -05:00
Author
Owner
Copy Link

@PureBlissAK commented on GitHub (Apr 18, 2026):

🤖 Automated Triage & Analysis Report

Issue: #15445
Analyzed: 2026-04-18T18:20:59.296945

Analysis

  • Type: unknown
  • Severity: medium
  • Components: unknown

Implementation Plan

  • Effort: medium
  • Steps:

This issue has been triaged and marked for implementation.

<!-- gh-comment-id:4274307540 --> @PureBlissAK commented on GitHub (Apr 18, 2026): <!-- ollama-issue-orchestrator:v1 issue:15445 --> ## 🤖 Automated Triage & Analysis Report **Issue**: #15445 **Analyzed**: 2026-04-18T18:20:59.296945 ### Analysis - **Type**: unknown - **Severity**: medium - **Components**: unknown ### Implementation Plan - **Effort**: medium - **Steps**: *This issue has been triaged and marked for implementation.*
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#35630
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?