Document common issues users encounter when using papermill

We should add a docs section which outlines common failures, why they happen, and how / where to look to address them. An example is linked below, but a few ideas come to mind:

• Kernel not found
• Kernel died (OOM + other reasons)
• New language not translating parameters
• Can't access input / output notebook paths
• Scheme not supported etc...

slack thread

Dennis [Yesterday at 6:11 PM] @here hello everyone, anyone ever experience the following issue when executing a spark notebook from within a Docker container via Papermill: RuntimeError: Kernel died before replying to kernel_info. I found a closed nteract/papermill github issue regarding this problem, but it did not specify a valid solution

3 replies

Dennis [16 hours ago] Sorry nevermind, issue resolved; I realize this has nothing to do with Papermill

betatim [7 hours ago] @Dennis do you think it is worth it to post on the issue you found to say “the problem has nothing to do with papermill, you should investigate X instead” for people from the future who experience this problem?

mseal [< 1 minute ago] I do think we should gather some of these common issues and put them in our docs for papermill, if nothing else because papermill is a touch point for many users and they often don't know how the underlying technologies are interacting.