Skip to content

jinja : coerce input for string-specific filters#21370

Merged
pwilkin merged 1 commit intomasterfrom
cisc/jinja-string-filter-coercion
Apr 3, 2026
Merged

jinja : coerce input for string-specific filters#21370
pwilkin merged 1 commit intomasterfrom
cisc/jinja-string-filter-coercion

Conversation

@CISC
Copy link
Copy Markdown
Member

@CISC CISC commented Apr 3, 2026

Overview

Coerce input for string-specific filters into string.

Additional information

String-specific filters will automatically coerce input to string in jinja2, this replicates that behavior.

Requirements

@github-actions github-actions bot added testing Everything test related jinja parser Issues related to the jinja parser labels Apr 3, 2026
@pwilkin pwilkin merged commit 1f34806 into master Apr 3, 2026
24 of 46 checks passed
@CISC CISC deleted the cisc/jinja-string-filter-coercion branch April 3, 2026 13:03
icex added a commit to icex/llama.cpp that referenced this pull request Apr 5, 2026
Includes:
- server: Fix undefined timing measurement errors (ggml-org#21201)
- server: save and clear idle slots on new task --clear-idle (ggml-org#20993)
- common: fix tool call type detection for nullable/enum schemas (ggml-org#21327)
- CUDA: fix FA kernel selection logic (ggml-org#21271)
- kv-cache: do not quantize SWA KV cache (ggml-org#21277) + revert (ggml-org#21332)
- common/parser: fix call ID detection + atomicity (ggml-org#21230)
- jinja: coerce input for string-specific filters (ggml-org#21370)
- Various CI, HIP, WebGPU, and documentation fixes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jinja parser Issues related to the jinja parser testing Everything test related

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: Chat Template Filter Error - 'upper' filter cannot be applied to Array type

3 participants