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

[GH-ISSUE #3580] codegemma models throwing weird outputs #27971

New Issue
Closed
opened 2026-04-22 05:38:41 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-22 05:38:41 -05:00
Owner
Copy Link

Originally created by @m-aebrer on GitHub (Apr 10, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/3580

Hi,

I see a lot of <|file_separator|> and similar sequences in the outputs. Is this something that should be fixed in the application consuming the outputs, or ollama?

$ ollama run codegemma:code
>>> int main()
 {.cpp
<|fim_prefix|>int main(){
int num1,num2,result;
num1=10;
num2=5;
result=num1+num2;
cout<<result;
return <|fim_suffix|><|fim_middle|>0;
}
<|file_separator|>

>>>

Originally posted by @fungiboletus in https://github.com/ollama/ollama/issues/3556#issuecomment-2046727592

Similarly, when using Continue with VSCode, I also see these file_separators being constantly suggested by the tab autocomplete. Not sure if it is fixed on the ollama side or on the continue side.

Originally created by @m-aebrer on GitHub (Apr 10, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/3580 Hi, I see a lot of `<|file_separator|>` and similar sequences in the outputs. Is this something that should be fixed in the application consuming the outputs, or ollama? ``` $ ollama run codegemma:code >>> int main() {.cpp <|fim_prefix|>int main(){ int num1,num2,result; num1=10; num2=5; result=num1+num2; cout<<result; return <|fim_suffix|><|fim_middle|>0; } <|file_separator|> >>> ``` _Originally posted by @fungiboletus in https://github.com/ollama/ollama/issues/3556#issuecomment-2046727592_ Similarly, when using Continue with VSCode, I also see these file_separators being constantly suggested by the tab autocomplete. Not sure if it is fixed on the ollama side or on the continue side.
GiteaMirror commented 2026-04-22 05:38:43 -05:00
Author
Owner
Copy Link

@jmorganca commented on GitHub (Apr 17, 2024):

Hi there, sorry about that. It seems the codegemma model on ollama.com didn't have all the required stop words - that should be fixed now if you re-pull

<!-- gh-comment-id:2060238002 --> @jmorganca commented on GitHub (Apr 17, 2024): Hi there, sorry about that. It seems the `codegemma` model on ollama.com didn't have all the required stop words - that should be fixed now if you re-pull
GiteaMirror commented 2026-04-22 05:38:45 -05:00
Author
Owner
Copy Link

@m-aebrer commented on GitHub (Apr 17, 2024):

awesome thank you!

<!-- gh-comment-id:2061899749 --> @m-aebrer commented on GitHub (Apr 17, 2024): awesome thank you!
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
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#27971
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?