Matthew Seal

Late response, but no there's not currently support for this in nbconvert. The library launches an isolated kernel process and manages it itself. Keeping a live kernel around and rehitting...

Take a look at https://github.com/nteract/papermill/issues/583, where someone used a custom engine to support reusing a kernel for each execution. It might fit what you're trying to do @marius311

That's very surprising that you see this on 3.13 with pip 24.3.1 -- I know this is an old issue but can you @AndreMCCarvalho give more details on the error...

Will look into copying more modern examples into the repo with upcoming changes, but closing this old issue for now.

I believe this was resolved via https://github.com/confluentinc/confluent-kafka-python/pull/787 which gives Generic Serdes API access for this information

Doesn't appear to be the ends-with-a-dot certificate name issue. As @allamiro mentioned this is likely a signing issue. If you can use the cert successfully independent of the python client...

Marking as wontfix as the the service needs to be upgraded to use later versions of schema registry.

Given you're on an old version of nbconvert I am guessing you're also on old versions of it'd dependencies. I do highly recommend upgrading versions and seeing if the issue...

FYI this should now be fixed in ipykernel 5.1.2 -- it was occurring if there were two kernels launched close to each other, with an unresolved race condition for the...

Hmm... how reproducible is the issue for you? How are you running nbconvert and is there any other processes or notebook related tasks running in parallel? Is the file system...