Skip to content

Clarify that CalleeHandled=false ThreadsafeFunction will not handle sync errors #352

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

Merged
Brooooooklyn merged 1 commit into from
Jul 30, 2025
Merged

Clarify that CalleeHandled=false ThreadsafeFunction will not handle sync errors #352

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions pages/docs/concepts/threadsafe-function.en.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -236,7 +236,9 @@ With this strategy, `ThreadsafeFunction` doesn't need to be called with `Result<
able to handle the error in the Rust threads, so you can't pass the `Error` back
to the JavaScript side.

It's only recommended if you are sure the threads where the `ThreadsafeFunction` is called will not return `Err` or panic.
The `ThreadsafeFunction` will also not be able to handle the synchronously thrown errors in the callback function. If you throw an synchronous error in the callback, it will cause the Node.js process to crash. Asynchronous errors (like `Promise` rejections) can be handled by the `ThreadsafeFunction`.

It's only recommended if you are sure the threads where the `ThreadsafeFunction` is called will not return `Err` or panic and the callback will not throw a synchronous error.

</Callout>

Expand Down Expand Up @@ -376,4 +378,4 @@ QueueFull
QueueFull
QueueFull
...
```
```