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

kernal info retrieval fails on small VMs #101

Closed
chrisjsewell opened this issue Aug 25, 2020 · 9 comments · Fixed by #102
Closed

kernal info retrieval fails on small VMs #101

chrisjsewell opened this issue Aug 25, 2020 · 9 comments · Fixed by #102

Comments

@chrisjsewell
Copy link
Contributor

This is essentially re-opening #95, because #96 adds extra debugging, but it does not fix it.

Basically on nearly every RTD run that calls nbclient, it fails intermittently and is super frustrating 😞 e.g. https://readthedocs.org/projects/sphinx-book-theme/builds/11733784/.
This has happened for both v0.2 and v0.4

The VM they are using is Standard_D1_v2

See: https://docs.microsoft.com/en-us/azure/virtual-machines/dv2-dsv2-series?toc=/azure/virtual-machines/linux/toc.json&bc=/azure/virtual-machines/linux/breadcrumb/toc.json#dv2-series

This may be related to #58

@davidbrochart
Copy link
Member

Did you try with master branch? If so, what does the exception say about info_msg['content']?

@chrisjsewell
Copy link
Contributor Author

No good point I should do that.
I messed around with it a load, and have tentatively got it to work, in this case, by removing a code cell.
If it is primarily a memory issue; the retrieval failing because of all the cell outputs now being held in memory, perhaps it would be helpful to put the language_info retrieval before the execution of the cells?

@davidbrochart
Copy link
Member

Yes I think it doesn't hurt putting the language_info retrieval before the execution. But if we are out of memory after the execution, we're in pretty bad shape anyway.

@chrisjsewell
Copy link
Contributor Author

Yeh exactly, I don't know if there is a deeper underlying cause (like memory leakage), but I think that would at least be a band aid

@chrisjsewell
Copy link
Contributor Author

chrisjsewell commented Aug 27, 2020

Thanks for merging 😄

FYI, I did just get an error from 0.4.2 on GH actions this time; https://github.com/executablebooks/jupyter-book/pull/911/checks?check_run_id=1035210652:

WARNING: /Users/runner/work/jupyter-book/jupyter-book/docs/file-types/notebooks.ipynb
Traceback (most recent call last):
  File "/Users/runner/hostedtoolcache/Python/3.7.9/x64/lib/python3.7/site-packages/jupyter_cache/executors/basic.py", line 147, in execute
    None,
  File "/Users/runner/hostedtoolcache/Python/3.7.9/x64/lib/python3.7/site-packages/jupyter_cache/executors/basic.py", line 155, in execute_single
    nb_bundle.nb, cwd=cwd, timeout=timeout, allow_errors=allow_errors,
  File "/Users/runner/hostedtoolcache/Python/3.7.9/x64/lib/python3.7/site-packages/jupyter_cache/executors/utils.py", line 56, in single_nb_execution
    record_timing=False,
  File "/Users/runner/hostedtoolcache/Python/3.7.9/x64/lib/python3.7/site-packages/nbclient/client.py", line 1082, in execute
    return NotebookClient(nb=nb, resources=resources, km=km, **kwargs).execute()
  File "/Users/runner/hostedtoolcache/Python/3.7.9/x64/lib/python3.7/site-packages/nbclient/util.py", line 74, in wrapped
    return just_run(coro(*args, **kwargs))
  File "/Users/runner/hostedtoolcache/Python/3.7.9/x64/lib/python3.7/site-packages/nbclient/util.py", line 53, in just_run
    return loop.run_until_complete(coro)
  File "/Users/runner/hostedtoolcache/Python/3.7.9/x64/lib/python3.7/asyncio/base_events.py", line 587, in run_until_complete
    return future.result()
  File "/Users/runner/hostedtoolcache/Python/3.7.9/x64/lib/python3.7/site-packages/nbclient/client.py", line 536, in async_execute
    'Content is:\n' + str(info_msg['content'])
RuntimeError: Kernel info received message content has no "language_info" key.Content is:
{'status': 'aborted'}

Could I be cheeky, and ask for a 0.4.3 release in the near future 😬

@davidbrochart
Copy link
Member

Sure, will do today!

@chrisjsewell
Copy link
Contributor Author

Legend!

@davidbrochart
Copy link
Member

0.4.3 is out.

@davidbrochart
Copy link
Member

0.5.0 is out, you should use it instead of 0.4.3, sorry!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants