Skip to content
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

refactor(jupyter): move ZeroMQ server to a separate thread #24373

Merged
merged 6 commits into from
Jul 2, 2024

Conversation

bartlomieju
Copy link
Member

@bartlomieju bartlomieju commented Jun 30, 2024

Moves the ZeroMQ messaging server to a separate thread.

This will allow to run blocking JS code and maintain communication
with the notebook frontend.

Towards #23592
Towards #24250
Closes #23617

cli/tools/jupyter/mod.rs Outdated Show resolved Hide resolved
}
});

let handle2 = deno_core::unsync::spawn({
let control_fut = deno_core::unsync::spawn({
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for renaming these.

Copy link
Member

@nathanwhit nathanwhit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@bartlomieju bartlomieju merged commit 7d919f6 into denoland:main Jul 2, 2024
17 checks passed
@bartlomieju bartlomieju deleted the jupyter_zeromq_thread branch July 2, 2024 22:38
zebreus pushed a commit to zebreus/deno that referenced this pull request Jul 8, 2024
…24373)

Moves the ZeroMQ messaging server to a separate thread.

This will allow to run blocking JS code and maintain communication
with the notebook frontend.

Towards denoland#23592
Towards denoland#24250
Closes denoland#23617
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Move jupyter zeromq code to separate thread & runtime
3 participants