Skip to content

Conversation

@dby-tmwctw
Copy link
Contributor

In the previous PR we addressed the problem where iopub comm messages generated by control channel have the wrong parent header from shell channel due to hard code. This PR move the logic to get_parent (following discussions here from @jasongrout and @minrk ) so we remove the hard-coding problem not only for the comm messages, but for other iopub messages as well.

@jasongrout jasongrout assigned minrk and unassigned minrk Jun 23, 2023
@jasongrout jasongrout requested a review from minrk June 23, 2023 23:02
@minrk
Copy link
Member

minrk commented Jun 26, 2023

Thanks!

@dby-tmwctw
Copy link
Contributor Author

Hi @minrk Thanks a lot for the approval! It's my first time contributing so may I know who to ask for merging this PR?

@minrk minrk merged commit a18f007 into ipython:main Jun 27, 2023
@minrk
Copy link
Member

minrk commented Jun 27, 2023

@dby-tmwctw I have merged it. I was waiting for CI to finish.

@blink1073
Copy link
Contributor

I'm on vacation this week, I can cut a release next week.

@SylvainCorlay
Copy link
Member

comm messages generated by control channel

While this PR complies with the spec, I would like to emphasize that according to the Jupyter kernel protocol specification, comm messages are only to be sent on the Shell channel and not the Control channel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants