Closed oxmwh closed 3 months ago
Hi @oxmwh - I'm not reproducing the bug with kaggle kernels pull <private>
; it works for me. Similarly, I think you have a slight bug in your code, as kernels_pull
requires an output path
api.kernels_pull('username/kernel-slug', 'output-dir')
With the output path, I'm able to download my private kernels.
Thank you so much @jplotts for your response.
I have created a notebook to reproduce the bug inside Kaggle itself.
Here is also a screenshot of the bug:
Hi @oxmwh - I see the problem now. It's not that the notebooks are private, it's that they have no versions. Permanent versions are created when a notebook is pushed via the API, or they can be created in the Notebook Editor UI via the "Save Version" button. I'll reopen this issue and file a bug internally to handle this case better. As a workaround in the meantime, creating a version of your notebook should enable you to pull it via the API.
OMG you're totally right! You're an angel from above!
Looks like @lucyhe fixed this one. I created another (internal) issue for push failing to create the first version and session of a kernel. (You need both version and session to exist to push a kernel.)
How to reproduce:
kaggle --version -> Kaggle API 1.6.2
kaggle kernels list -m
works correctly (shows both private and public kernels) butkaggle kernels pull
orkaggle kernels status
on my private kernels gives:404 - Not Found - Not found
They work fine on my public kernels though. Same 404 results using python like so: