-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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.
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
fix(rust): Fix sink_ipc_cloud
panicking with a Tokio runtime error
#14262
Conversation
make CloudWriter call `get_runtime().block_on` from a newly spawned thread.
ef4ae59
to
87af454
Compare
e8f3e67
to
eca2306
Compare
sink_ipc_cloud
panicking with a Tokio runtime error
Hi @stinodego! I am sorry for the ping, but is there something blocking this PR or something we could do to get it merged? Thank you! ❤️ |
I'm still available to (help) fix(ing) the merge conflicts once more if needed, but it would be nice if it can be merged soon afterwards before new conflicts would arise 😅 |
I think this one can be closed as there has changed a lot since then. |
Is a fix still accepted? The functionality is currently broken and we would be happy users of it. Thank you :) |
Yes, it is accepted. But I believe it was fixed by #18027 |
I'm afraid this was not fixed yet. I could reproduce the error with the latest version from the main branch. Here is the backtrace: https://gist.github.com/philss/a81fab6f9cf85d23a0f1c364633e992b |
Fixes pola-rs#13614 When writing to ObjectStore-compatible storage using the IPC format, it seems like the `block_on` calls inside the constructed `CloudWriter` might sometimes get called inside another `block_on` call. Tokio does not like this, resulting in a panic. This PR resolves this issue by using `block_on_potential_spawn` in the necessary places instead. This is a fix that was originally written by @Qqwy in another PR: pola-rs#14262 Co-Authored-By: Qqwy / Marten <[email protected]>
Fixes pola-rs#13614 When writing to ObjectStore-compatible storage using the IPC format, it seems like the `block_on` calls inside the constructed `CloudWriter` might sometimes get called inside another `block_on` call. Tokio does not like this, resulting in a panic. This PR resolves this issue by using `block_on_potential_spawn` in the necessary places instead. This is a fix that was originally written by @Qqwy in another PR: pola-rs#14262 Co-Authored-By: Qqwy / Marten <[email protected]>
Fixes pola-rs#13614 When writing to ObjectStore-compatible storage using the IPC format, it seems like the `block_on` calls inside the constructed `CloudWriter` might sometimes get called inside another `block_on` call. Tokio does not like this, resulting in a panic. This PR resolves this issue by using `block_on_potential_spawn` in the necessary places instead. This is a fix that was originally written by @Qqwy in another PR: pola-rs#14262 Co-Authored-By: Qqwy / Marten <[email protected]>
Fixes pola-rs#13614 When writing to ObjectStore-compatible storage using the IPC format, it seems like the `block_on` calls inside the constructed `CloudWriter` might sometimes get called inside another `block_on` call. Tokio does not like this, resulting in a panic. This PR resolves this issue by using `block_on_potential_spawn` in the necessary places instead. This is a fix that was originally written by @Qqwy in another PR: pola-rs#14262 Co-Authored-By: Qqwy / Marten <[email protected]>
Fixes #13614
When writing ot ObjectStore-compatible storage in the IPC format, it seems like the
.block_on
calls inside the constructedCloudWriter
might sometimes get called inside anotherblock_on
call. Tokio does not like this, resulting in a panic.This PR resolves this issue by using
block_on_potential_spawn
in the necessary places instead.