Skip to content

Eval bug: c4ai-command-r7b-12-2024 unable to use #11443

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
rhjdvsgsgks opened this issue Jan 27, 2025 · 6 comments · Fixed by #11574
Closed

Eval bug: c4ai-command-r7b-12-2024 unable to use #11443

rhjdvsgsgks opened this issue Jan 27, 2025 · 6 comments · Fixed by #11574
Assignees

Comments

@rhjdvsgsgks
Copy link
Contributor

Name and Version

caf773f

Operating systems

Linux

GGML backends

Vulkan

Hardware

not relevant

Models

c4ai-command-r7b-12-2024 q8

Problem description & steps to reproduce

run it with llama server. got error

First Bad Commit

maybe 6171c9d

Relevant log output

terminate called after throwing an instance of 'std::runtime_error'
  what():  Expected block keyword at row 152, column 17:
        {%- else %}
            {%- break %}
                ^
        {%- endif %}
@dranger003
Copy link
Contributor

Looks like you are using the jinja template option, which I don't believe supports the template for this model (at least not yet).

@rhjdvsgsgks
Copy link
Contributor Author

Looks like you are using the jinja template option, which I don't believe supports the template for this model (at least not yet).

i didn't enable it explicitly. is it enabled by default?

@dranger003
Copy link
Contributor

Can you try --chat-template command-r maybe? The help says --jinja should be disabled by default.

@arch-btw
Copy link
Contributor

Having the same issue when I haven't enabled jinja. But like @dranger003 said --chat-template command-r works.

@rhjdvsgsgks
Copy link
Contributor Author

Can you try --chat-template command-r maybe? The help says --jinja should be disabled by default.

yes. it solved the error

@ochafik
Copy link
Collaborator

ochafik commented Jan 31, 2025

Hey @rhjdvsgsgks, @dranger003, thanks for reporting / investigating this! Some quick thoughts:

@ochafik ochafik self-assigned this Jan 31, 2025
@ochafik ochafik mentioned this issue Feb 1, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants