Kevin Bates

@manmedia - great news - glad to hear you're moving forward. Given the circumstances here (particularly the lack of reproducibility), I'm not surprised this was a host OS issue. I...

> I disagree that there is no reproducibility - the information shared above could be used to disprove or prove what I have found - by another person under the...

Hi @blair-anson - thanks for opening this issue. The `EG_`-prefixed envs that appear to be set on your client (notebook) server apply to the EG instance itself and need to...

Only the active kernels request should be getting proxied to the Gateway. Terminal and session requests will be handled by the server. You should also see periodic requests (about every...

Back to your issue. Have you modified `elyra/kernel-py:2.6.0` in any way? What is contained in the kernel pod's logs? Note that this can be tricky to capture, especially if your...

Hi @blair-anson - what is perplexing to both @rahul26goyal and me is that that code is responsible for receiving the kernel connection information from the remote kernel (pod in this...

Also, if you're in a position to try EG 3.0.0rc0, that would be great! That would serve as another datapoint and bring you up to date on the main branch.

FWIW - I just deployed EG 2.6.0 in my kubernetes cluster and get the following log entries... The expected startup banner... ``` [I 2022-09-24 15:16:23.120 EnterpriseGatewayApp] Jupyter Enterprise Gateway 2.6.0...

Thank you for the detailed response! This is extremely odd - I definitely see what you mean by "spamming the log"! We've never seen this before and can't reproduce this....

Hi @blair-anson - Could you please send a copy of the `launch_ipykernel.py` file located in the `/usr/local/bin/kernel-launchers/python/scripts` of your kernel pod's image, and a copy of **both files** in the...