[Bug] Papermill hangs when running in container #684
Labels
Comments
|
I had the same problem after rebuilding my docker image. Papermill in my old image worked but in the new one it refused to work, I had the same outputs, the first cell never completed. I spend 3 days searching for the cause I found out that it is a dependency problem and with trial and error I found the culprit: |
|
That looks suspiciously like some issue with async loop configuration or modifications. Can you list the wider list of packages that are locally installed and if you have any init code or modifications to the async loop settings? What OS are you on as well? |
|
I am using base image There are installed packages listed with Unfortunately I already made some modifications to my docker image(updated airflow) so many different packages were updated. |
|
I am experiencing this too, running papermill inside a systemd-nspawn container In addition to this, since installing papermill, executing notebooks through jupyter-nbconvert fails. I believe this was caused becasue as papermill got installed, nbbclient was updated. This updated updated jupyter-client too, but did not update jupyter-console I ended up with jypyter client v7.3.5 and jypyter console v6.0.0 This is the error shown when executing jupyte nbconvert --execute with those vresions installed, perhaps it sheds some light on this problem:
A different solution to updating jupyter-console is to downgrade jupyter-client to v6.1.2 |
|
Looks like this is also being discussed over at scikit-hep/pyhf#2104. The workaround seems to be to constrain EditOops, looks like this is a duplicate of #711 as well. There is more info over there. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🐛 Bug
Hi there,
I'm running papermill in a devcontainer just to try it out, and found it hangs when trying to execute the first cell.
after ctrl+C
The notebook runs fine via the UI or
pytest --nbmake.Versions
Thanks for your work on this library!
The text was updated successfully, but these errors were encountered: