Skip to content

Misc. bug: Inconsistent handling of boolean command line arguments in environment #16105

@sawntoe

Description

@sawntoe

Name and Version

version: 6517 (69ffd89)
built with cc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0 for x86_64-linux-gnu

Operating systems

Linux

Which llama.cpp modules do you know to be affected?

llama-server

Command line

llama-server

Problem description & steps to reproduce

LLAMA_ARG_JINJA env variable only accepts true and false does not accept truthy arguments like enabled or disabled unlike other variables like LLAMA_FLASH_ATTN. This discrepancy is made worse by the fact that the terminology used to describe boolean variables in environment in the doc is enabled/disabled, and there is nothing in the log to indicate whether jinja has been enabled or not. Needless to say this has and will cause much headaches to anyone attempting to configure llama-server via environment variables.

First Bad Commit

No response

Relevant log output

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions