BoundaryML/baml - CodSpeed

baml

Blog Docs Changelog

Performance History

Latest Results

chore: Bump version to 0.213.0 (#2701) Bump version to 0.213.0 ❌ Typescript integ tests ❌ Python integ tests Generated by bump-version script.  --- > [!NOTE] > Bumps all packages and tooling to 0.213.0 and updates changelogs; propagates version across language clients and IDE extensions with a minor dependency tweak. > > - **Release: 0.213.0** > - Update `CHANGELOG.md` and docs (`fern/pages/changelog.mdx`) with 0.213.0 notes (bug fixes, features, chores). > - **Version Bumps** > - Set workspace/package versions to `0.213.0` across `engine/Cargo.toml`, language clients (`Go`, `Python`, `Ruby`, `TypeScript`), IDE extensions (`VSCode`, `JetBrains`, `Zed`), and integration generators (`integ-tests/*`). > - Update generated client version guards/messages in TS/React/ESM and Python clients. > - **Tooling/Configs** > - Sync bumpversion configs under `tools/versions/*` to `0.213.0`. > - Cargo lock updates reflect internal crates at `0.213.0`; adjust `dir-writer` dep `pathdiff` to `0.1.0`. > - **Tests/Artifacts** > - Refresh integration test outputs (e.g., `junit.xml`) to align with the new version. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 575056242a978115308aacd961be6466e2a772a7. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup>

canary

20 hours ago

add invalid unicode syntax and rust-as-baml tests

greg/parse-expr-and-statement

20 hours ago

Fix timeout exceptions for streaming LLM calls (#2699) Prior to this PR, the `request_timeout_ms` was implemented in a way that quietly cancelled the LLM response. This PR checks, after the response finishes, whether or not the LLM provider's stop signal was received by the runtime, and when not received, returns a response failures, which gets turned into the appropriate exception downstream.

canary

21 hours ago

add invalid unicode syntax and rust-as-baml tests

greg/parse-expr-and-statement

21 hours ago

fix: select earliest successful LLM call by lexicographic request_id order (#2692) ### Issue Reference This PR fixes #2451 ### Summary Updated LLM call selection logic to correctly pick the earliest successful call by lexicographic `HttpRequestId` ordering. This ensures deterministic selection when multiple successful calls exist. ### Changes This PR addresses an issue where the code prioritized completion time instead of lexicographically earliest ulid uuid. 1. Filter to keep only candidates where `is_success = true` 2. Sort these successful candidates by http request id, ulid uuid, lexicographically) 3. Choose the first candidate from this sorted list ### Details - Filters candidates to only successful calls - Sorts by `request_id.to_string()` lexicographically (since `HttpRequestId` lacks `Ord`) - Picks the first entry in the sorted list - Verified via `cargo test -p baml-runtime -q`  --- > [!NOTE] > Refactors LLM call selection to pick the earliest successful call by lexicographic HttpRequestId and marks only that call as selected, with new tests covering success-vs-failure and ordering. > > - **Tracing/FunctionLog (storage.rs)** > - Refactor LLM call assembly: introduce `CallCandidate` to gather data for each `request_id`. > - Selection logic: filter successful candidates, sort by `request_id.to_string()` lexicographically, select the first; mark only that call as `selected` across `Basic` and `Stream` kinds. > - **Tests** > - Add `test_selected_call_prefers_success_over_failure` and `test_selected_call_chooses_earlier_success_if_last_failed` to verify selection behavior. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 9a3143e20bda42c8876ca1fae72d16c8cdf592c4. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup>  --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: aaron <aaron@boundaryml.com>

canary

2 days ago

default request timeout is too low (#2698)  > [!NOTE] > Raise default `request_timeout_ms` from 30s to 5m for regular (non-composite) clients; composite clients unchanged. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 3e60ae788421451f958cf9c5b76dd88bc672085b. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup>

canary

2 days ago

fix bug in baml-cli init (#2697)  > [!NOTE] > Harden init UI and error handling with TTY detection, safe cleanup, and non-interactive fallbacks, and exclude an additional test in CI. > > - **CLI (init UI)**: > - Add TTY detection using `IsTerminal`; only initialize UI when `stdout` is a TTY and gracefully fallback if UI creation fails. > - Ensure terminal state cleanup: disable raw mode on errors and after error UI; keep content and exit alternate screen reliably. > - Non-interactive fallback: print steps, completion (✓), and failures (✗) to stdio/stderr when UI is unavailable. > - Refactor error display: `show_error` checks TTY and delegates to `show_error_ui`; fallback to plain stderr message if UI fails. > - **Tests**: > - Exclude `tests/providers/test_aws_video_request.py` in `integ-tests/python/run_tests.sh`. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 8a8324fbe86a4e144b1934bb0cf3f989fc653975. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup>

canary

2 days ago

Parse class constructors, maps and generics (#2696)

greg/parse-expr-and-statement

2 days ago

Active Branches

Parse expr and statement into CST

last run

20 hours ago

-14%

Refactor parser implementation with improved tree structure and error recovery

last run

3 days ago

-38%

© 2025 CodSpeed Technology

Home Terms Privacy Docs