Since upgrading baml to 0.215.2 I'm experiencing internal panics when calling functions (via OpenRouter clients for context). thread '' panicked at /Users/runner/work/baml/baml/engine/baml-lib/jsonish/src/deserializer/semantic_streaming.rs:130:26: This field is guaranteed to be in the field set note: run with

RUST_BACKTRACE=1

environment variable to display a backtrace File "/Users/mike/fabula/fabula_v2/baml_client/sync_client.py", line 482, in ParseSingleSceneElements __result__ = self.__options.merge_options(baml_options).call_function_sync(function_name="ParseSingleSceneElements", args={ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/mike/fabula/fabula_v2/baml_client/runtime.py", line 172, in call_function_sync return __runtime__.call_function_sync( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ pyo3_runtime.PanicException: This field is guaranteed to be in the field set

oh that is very odd...

do you have a repro that consistently throws this?

It's actually not specific to a baml class and happened in different places in my pipeline with 0.215.2 - downgraded to 0.210 and no more issues. I thought it odd too as I don't have streaming enabled

Ok i have a feeling i know what this is so we will take a look for 0.217.0

No I don't use streaming at all. I can share the pvt repo if its helpful

yeah that would be amazing