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

[GH-ISSUE #12387] Add fill-in-the-middle (FIM) support for qwen3-coder #54741

New Issue
Open
opened 2026-04-29 07:09:16 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-29 07:09:16 -05:00
Owner
Copy Link

Originally created by @drifkin on GitHub (Sep 23, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/12387

Originally assigned to: @drifkin on GitHub.

qwen3-coder was trained for FIM support, as seen here: https://github.com/QwenLM/Qwen3-Coder?tab=readme-ov-file#fill-in-the-middle-with-qwen3-coder

The qwen3-coder renderer should be updated with suffix support.

Originally created by @drifkin on GitHub (Sep 23, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/12387 Originally assigned to: @drifkin on GitHub. qwen3-coder was trained for FIM support, as seen here: https://github.com/QwenLM/Qwen3-Coder?tab=readme-ov-file#fill-in-the-middle-with-qwen3-coder The qwen3-coder renderer should be updated with suffix support.
GiteaMirror added the feature request label 2026-04-29 07:09:16 -05:00
GiteaMirror commented 2026-04-29 07:09:18 -05:00
Author
Owner
Copy Link

@itsjavi commented on GitHub (Dec 20, 2025):

I see, this is one of the reasons I could not use it for Void IDE autocompletion. stable-code seems to have the same issue.

<!-- gh-comment-id:3677414696 --> @itsjavi commented on GitHub (Dec 20, 2025): I see, this is one of the reasons I could not use it for Void IDE autocompletion. `stable-code` seems to have the same issue.
GiteaMirror commented 2026-04-29 07:09:23 -05:00
Author
Owner
Copy Link

@darthbanana13 commented on GitHub (Feb 15, 2026):

Maybe a stupid question, but how was this issue considered/labeled a bug, and this current one, which is actually deferred from the same issue mentioned, considered a feature request? I believe one of the two is mislabeled.

<!-- gh-comment-id:3904296240 --> @darthbanana13 commented on GitHub (Feb 15, 2026): Maybe a stupid question, but how was [this issue ](https://github.com/ollama/ollama/issues/11621) considered/labeled a bug, and this current one, which is actually deferred from the same issue mentioned, considered a feature request? I believe one of the two is mislabeled.
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 feature request
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#54741
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?