`id_no` cannot be used as an identifier for the kernel

[viocha]

First, I created a kernel using an id_no = 145717001

> kaggle kernels push
Kernel version 1 successfully pushed.  Please check progress at https://www.kaggle.com/code/vioochai/tmp001

{
  "id_no": 145717001,
  "title": "tmp001",
  "code_file": "notebook.ipynb",
  "language": "python",
  "kernel_type": "notebook",
  "is_private": true,
  "enable_internet": true
}

When I removed the title field and tried to modify the kernel using the same id_no, it prompted that I was creating a new kernel.

> kaggle kernels push
Kernel push error: New kernels must have a title specified

{
  "id_no": 145717001,
  "code_file": "notebook.ipynb",
  "language": "python",
  "kernel_type": "notebook",
  "is_private": true,
  "enable_internet": true
}

When I added the title field back, it indicated a kernel conflict.

> kaggle kernels push
409 Client Error: Conflict for url: https://www.kaggle.com/api/v1/kernels/push

{
  "id_no": 145717001,
  "title": "tmp001",
  "code_file": "notebook.ipynb",
  "language": "python",
  "kernel_type": "notebook",
  "is_private": true,
  "enable_internet": true
}

I speculate that it works like this: it uses the provided title and your username to create an id = username/title to identify the kernel, completely ignoring the role of id_no. This contradicts the API documentation which states that id_no has higher priority.

[stevemessick]

This contradicts the API documentation which states that id_no has higher priority.

Unfortunately, the wiki documentation for kernel metadata has been out-of-date since 4/13/2021. That was when a specific check was added to the server to ensure id (<username>/<title>) was used.

We're in the process of cleaning up the documentation, so this problem will be resolved soon-ish.

[stevemessick]

Oops, I mis-read the code. It isn't that simple. I'll try to figure out the root problem.