Issues

Official installer wrapper requires GLIBC 2.39 and cannot bootstrap on Debian bookworm

#4624

· BenSpex opened

on Aug 28, 2026

OpenAI-compat: openai-generic named client with /v1 base_url, not openai or openai-responses

#4620

· cursor opened

on Aug 28, 2026

0.17.0 parser: an optional class field is parsed as null when ≥2 of its optional fields are absent (present object with all required fields)

#4610

· BenSpex opened

on Aug 27, 2026

0.17.1 nightlies remove `#"…"#` hash string literals (E0098) with no render-preserving migration path — the backtick replacement dedents indent-bearing prompt fragments

#4591

· BenSpex opened

on Aug 25, 2026

SAP silently discards array elements it cannot coerce — `baml run` returns exit 0 with fewer rows and NO signal on any channel (stdout, stderr, `--output-format debug`, `--log-file`, `BAML_LOG`)

#4590

· BenSpex opened

on Aug 25, 2026

`baml run` on 0.17.0 swallows every thrown error and prints a type-checker union dump instead (0.15.0 reported the real error)

#4588

· BenSpex opened

on Aug 25, 2026

0.17.0: `throws` clause with an unresolved type panics the compiler (index out of bounds, type_ref.rs:346, exit 134) — 0.16.0 gives a clean E0002

#4587

· BenSpex opened

on Aug 25, 2026

0.17.0: `baml.json.json` client option (`request_body`) rejects a map literal — only `baml.json.parse` of a hand-escaped string works

#4586

· BenSpex opened

on Aug 25, 2026

0.15→0.17 openai-generic wire change: `messages[].content` part array became a plain string — intentional? needs a migration note (breaks byte-stable request consumers)

#4585

· BenSpex opened

on Aug 25, 2026

0.17.0 rejects unary `!` on `bool | null` (E0001) that 0.15/0.16 type-check but panic on at runtime (`VM internal error: cannot apply unary operation: ! any`)

#4584

· BenSpex opened

on Aug 25, 2026

Optional EvalPort interop for .baml test blocks

#4559

· adhabnr-ux opened

on Aug 22, 2026

[bug] 0.17.0 canary: internal compiler error on unknown method when generic type arguments are inferred

#4506

· ritunjaym opened

on Aug 18, 2026

Navigation Menu

Uh oh!

All issues

Official installer wrapper requires GLIBC 2.39 and cannot bootstrap on Debian bookworm

OpenAI-compat: openai-generic named client with /v1 base_url, not openai or openai-responses

0.17.0 parser: an optional class field is parsed as null when ≥2 of its optional fields are absent (present object with all required fields)

0.17.1 nightlies remove `#"…"#` hash string literals (E0098) with no render-preserving migration path — the backtick replacement dedents indent-bearing prompt fragments

SAP silently discards array elements it cannot coerce — `baml run` returns exit 0 with fewer rows and NO signal on any channel (stdout, stderr, `--output-format debug`, `--log-file`, `BAML_LOG`)

`baml run` on 0.17.0 swallows every thrown error and prints a type-checker union dump instead (0.15.0 reported the real error)

0.17.0: `throws` clause with an unresolved type panics the compiler (index out of bounds, type_ref.rs:346, exit 134) — 0.16.0 gives a clean E0002

0.17.0: `baml.json.json` client option (`request_body`) rejects a map literal — only `baml.json.parse` of a hand-escaped string works

0.15→0.17 openai-generic wire change: `messages[].content` part array became a plain string — intentional? needs a migration note (breaks byte-stable request consumers)

0.17.0 rejects unary `!` on `bool | null` (E0001) that 0.15/0.16 type-check but panic on at runtime (`VM internal error: cannot apply unary operation: ! any`)

Optional EvalPort interop for .baml test blocks

[bug] 0.17.0 canary: internal compiler error on unknown method when generic type arguments are inferred

Uh oh!

Search results