New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Calling a BAML function in a celery worker on darwin-arm64 reliably triggers a SIGSEGV #778

Closed

sxlijin opened this issue Jul 11, 2024 · 1 comment

Collaborator

sxlijin commented Jul 11, 2024

Repro instructions on my machine

Log message: https://gist.github.com/sxlijin/5575618890e39386c5494deb1051974f

Contributor

hellovai commented Jul 19, 2024 •

edited

Loading

This is resolved now thanks to #803 (confirmed and tested that a crash NEVER happens when using celery with sync interfaces).

The bug was caused by UB of async futures mixing poorly with FFI boundaries and pickling from multiprocessing.

As long as a user uses the new sync interface exposed by baml, crashes should not happen.

hellovai closed this as completed

BoundaryML deleted a comment from greptile-apps bot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment