[ark] kernel_info_request not getting kernel_info_reply
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 337
- Forks
- 32
- Avg merge
- 8d 17h
- Merged PRs (30d)
- 11
Description
I'm trying out the Ark kernel with my Zed PR (https://github.com/zed-industries/zed/pull/13625) and running into an issue with Ark no longer able to respond to execute_requests after a kernel_info_request is sent. Since it seems to work well in the classic Jupyter notebook, this is probably on my end. My shell socket is stuck waiting for a kernel_info_reply that never comes. Meanwhile I do get the status: busy and status: idle messages on the IOPUB channel. If I just don't send a KernelInfoRequest then all is well.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Ark kernel flow from the referenced Zed PR, sending a kernel_info_request before an execute_request and observing the shell and IOPUB channels. Compare the exchange with classic Jupyter, focusing on why kernel_info_reply is absent; done means the reply arrives and later execute_request messages receive normal responses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter, r
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100