fix TimeoutError and InvalidArgumentError getting raised as BamlError

[aaronvg]

Note

Improves error fidelity and context for runtime failures.

• Preserves TimeoutError when LLMResponse is an LLMFailure with ErrorCode::Timeout instead of converting to ValidationError (types/response.rs)
• Uses anyhow::Context to attach messages to underlying errors for FunctionNotFound and InvalidParams in prepare_function, keeping original cause chains (prepare_function.rs)
• Minor test cleanups: formatting, clearer pytest.skip strings, and capturing/printing exception info in test_parameter_failing_assert (test_functions.py)

^{Written by Cursor Bugbot for commit d9ee4ca. This will update automatically on new commits. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
promptfiddle	Ready	Preview, Comment	Jan 9, 2026 8:41pm

[cursor]

Error details lost when converting to string for tracing

Medium Severity

The change from anyhow::anyhow!(format!("...: {error}")) to error.context(...) alters how the error is displayed when converted to a string. In anyhow, Display for an error with context only shows the outermost message, not the full chain. Since the consuming code at lib.rs:1415 uses anyhow::anyhow!("{}", err_anyhow) to set errors for tracing, the original underlying error message is now lost in traces. Previously, the formatted string included both the context and the original error; now only the context appears in trace logs, making debugging harder.