Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

C# research kernel idle infinitely #414

Open
LouisSzeto opened this issue Oct 21, 2022 · 5 comments
Open

C# research kernel idle infinitely #414

LouisSzeto opened this issue Oct 21, 2022 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@LouisSzeto
Copy link
Contributor

Right after connected to the jupyter, C# research notebook's Foundation-C#-default kernel went idle forever, and cannot be activated by running cells. Now, we can only restart with a new kernel instance and run all cells before its connection with the host to get the cells executed at the instance of connection.

@Martin-Molinero Martin-Molinero added the bug Something isn't working label Oct 21, 2022
@LouisSzeto
Copy link
Contributor Author

Note:

  1. Jupyterlab version doesn't matter, version 3.2.1 to 3.4.4 have the same issue.
  2. Connection to docker container didn't end
  3. The below error message will pop up if running cells after it was disconnected:
[W 2022-10-21 17:29:13.900 ServerApp] Nudge: attempt 10 on kernel {}
[W 2022-10-21 17:29:18.926 ServerApp] Nudge: attempt 20 on kernel {}
[W 2022-10-21 17:29:23.949 ServerApp] Nudge: attempt 30 on kernel {}
[W 2022-10-21 17:29:28.973 ServerApp] Nudge: attempt 40 on kernel {}
[W 2022-10-21 17:29:33.998 ServerApp] Nudge: attempt 50 on kernel {}
[W 2022-10-21 17:29:39.021 ServerApp] Nudge: attempt 60 on kernel {}
[W 2022-10-21 17:29:44.052 ServerApp] Nudge: attempt 70 on kernel {}
[W 2022-10-21 17:29:49.079 ServerApp] Nudge: attempt 80 on kernel {}
[W 2022-10-21 17:29:54.104 ServerApp] Nudge: attempt 90 on kernel {}
[W 2022-10-21 17:29:59.127 ServerApp] Nudge: attempt 100 on kernel {}
[W 2022-10-21 17:30:04.148 ServerApp] Nudge: attempt 110 on kernel {}
[W 2022-10-21 17:30:09.172 ServerApp] Nudge: attempt 120 on kernel {}
[E 2022-10-21 17:30:09.386 ServerApp] Uncaught exception GET
/api/kernels/{abcabc}/channels?session_id={xyz} (172.18.0.1)
    HTTPServerRequest(protocol='http', host='localhost:8080', method='GET',
uri='/api/kernels/{abcabc}/channels?session_id={xyz}
version='HTTP/1.1', remote_ip='172.18.0.1')
    Traceback (most recent call last):
      File "/opt/miniconda3/lib/python3.8/site-packages/tornado/websocket.py", line 956, in _accept_connection
        await open_result
    tornado.util.TimeoutError: Timeout

@Martin-Molinero Martin-Molinero transferred this issue from QuantConnect/lean-cli Oct 25, 2022
@Martin-Molinero
Copy link
Member

This issue seems to have started since the py38 update at QuantConnect/Lean#6558

@Martin-Molinero Martin-Molinero self-assigned this Oct 25, 2022
@Martin-Molinero
Copy link
Member

Reported bugs for jupyter lab & dotnet interactive

@Martin-Molinero
Copy link
Member

  • We could potentially make the lean CLI run the notebook with net in host mode to get around this issue

@Martin-Molinero
Copy link
Member

We could potentially make the lean CLI run the notebook with net in host mode to get around this issue

Sadly network host mode is only currently working for linux see docker/roadmap#238

@Martin-Molinero Martin-Molinero transferred this issue from QuantConnect/Lean Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Backlog
Development

No branches or pull requests

2 participants