I am testing out an upgrade from 0.214.0 to 0.216.0 and receiving this stack: goroutine 6 [running]: backend-1 | reflect.valueInterface({0x0?, 0x0?, 0x8eff8e7?}, 0xc?) backend-1 | /usr/local/go/src/reflect/value.go:1478 +0xfa backend-1 | reflect.Value.Interface(...) backend-1 | /usr/local/go/src/reflect/value.go:1473 backend-1 | github.com/boundaryml/baml/engine/language_client_go/baml_go/raw_objects.decodeObjectResponse(0xc00136e000?, 0x6?) backend-1 | /go/pkg/mod/github.com/boundaryml/baml@v0.216.0/engine/language_client_go/baml_go/raw_objects/utils.go:184 +0x19a backend-1 | github.com/boundaryml/baml/engine/language_client_go/baml_go/raw_objects.CallMethod({0x94f7520, 0xc0021f3100}, {0x8efda0c, 0xb}, 0xc0007942a8?) backend-1 | /go/pkg/mod/github.com/boundaryml/baml@v0.216.0/engine/language_client_go/baml_go/raw_objects/utils.go:146 +0x3e7 backend-1 | github.com/boundaryml/baml/engine/language_client_go/baml_go/raw_objects.destructor({0x94f7520?, 0xc0021f3100?}) backend-1 | /go/pkg/mod/github.com/boundaryml/baml@v0.216.0/engine/language_client_go/baml_go/raw_objects/utils.go:99 +0x2f backend-1 | github.com/boundaryml/baml/engine/language_client_go/baml_go/raw_objects.decodeRawObject.func1({0x94f7520, 0xc0021f3100}) backend-1 | /go/pkg/mod/github.com/boundaryml/baml@v0.216.0/engine/language_client_go/baml_go/raw_objects/utils.go:204 +0x25 backend-1 | runtime.runFinalizers() backend-1 | /usr/local/go/src/runtime/mfinal.go:272 +0x425 backend-1 | Process Exit with Code: 2

thanks for the report -- sorry about that. Does it happen on every call?

I believe some calls succeeded.

will tag @Vaibhav (BAML 🐑) since he's on some FFI work at the moment -- he may have patched for 0.217.0

i haven't seen that recently so I think that one can be closed

we patched one ocurrence of this in 0.217.0

Thanks! testing now

the next batch of fixes will go out with this: https://github.com/BoundaryML/baml/pull/2978/files (also related to this error)