docs(jupyter-notebook): document zmq transport fallback and disable_check_xsrf pitfalls - #70482
Merged
Conversation
…e_check_xsrf pitfalls Add two pitfalls discovered when running the skill against a fresh Jupyter server: - Pitfall #9: When the websocket reply channel hangs on every execute even though the kernel actually ran (REST shows execution_state=idle and execution_count increments), force zmq transport with --transport zmq. The zmq transport uses jupyter_client directly and sidesteps the broken websocket layer. - Pitfall #10: A fresh ServerApp rejects POST /api/sessions with "_xsrf argument missing from POST" unless you start it with --ServerApp.disable_check_xsrf=True. Needed for REST-only flows where no browser/cookie is establishing the XSRF token.
Regenerate the auto-gen skill page and translate pitfalls 9-10 into the zh-Hans mirror, following the cherry-picked pitfall additions.
Contributor
૮ >ﻌ< ა ci reviewran on 1158d50 all good! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Salvages #27283 by @upicat — documents two easy-to-misdiagnose pitfalls in the
jupyter-notebookskill (formerlyjupyter-live-kernel, moved to optional-skills in #70431 after the PR was opened).executeeven though the kernel ran fine (REST showsexecution_state=idle,execution_countincrements). Fix:--transport zmqto drive the kernel via jupyter_client directly.disable_check_xsrffor REST-only flows: a fresh ServerApp rejectsPOST /api/sessionswith'_xsrf' argument missing from POSTsince no browser ever establishes a token. Fix: start with--ServerApp.disable_check_xsrf=True.Changes
optional-skills/data-science/jupyter-notebook/SKILL.md: pitfalls 9–10 added (cherry-picked from docs(jupyter-live-kernel): document zmq transport fallback and disable_check_xsrf pitfalls #27283, git rename detection applied it to the new path; authorship preserved)contributors/emails/: upicat mapping addedValidation
Infographic