Running notebooks are not deleted correctly

[tariqrahiman]

I created a notebook named foo.ipynb
Then in the home screen under Your notebooks - i clicked on the delete button for deleting foo.ipynb
Note:
Your notebook is currently running. It will be closed before delete.

I proceed.
However, we can see that under Your notebooks - foo.ipynb is deleted but under Running notebooks you can still see the deleted notebook.

[tariqrahiman]

@pplonski Logs - not sure if this will help to you debug the issue

[W 07:49:06.416 NotebookApp] 404 DELETE /api/sessions/9e12b8af-3890-4402-b747-a3255842d43e?token=my_very_secret_token (127.0.0.1): Session not found: session_id='9e12b8af-3890-4402-b747-a3255842d43e'
[W 07:49:06.417 NotebookApp] Session not found: session_id='9e12b8af-3890-4402-b747-a3255842d43e'
[W 07:49:06.418 NotebookApp] 404 DELETE /api/sessions/9e12b8af-3890-4402-b747-a3255842d43e?token=my_very_secret_token (127.0.0.1) 2.990000ms referer=None
[I 07:50:04.429 NotebookApp] Uploading file to /foo.ipynb
ERROR:asyncio:Exception in callback <TaskWakeupMethWrapper object at 0x0000020B4513FF40>(<Future finis...0e1"\r\n\r\n'>)
handle: <Handle <TaskWakeupMethWrapper object at 0x0000020B4513FF40>(<Future finis...0e1"\r\n\r\n'>)>
Traceback (most recent call last):
File "C:\Users\Owner\AppData\Roaming\MLJAR-Studio\miniconda\lib\asyncio\events.py", line 80, in _run
self._context.run(self._callback, *self._args)
RuntimeError: Cannot enter into task <Task pending name='Task-3' coro=<HTTP1ServerConnection._server_request_loop() running at C:\Users\Owner\AppData\Roaming\MLJAR-Studio\miniconda\lib\site-packages\tornado\http1connection.py:823> wait_for=<Future finished result=b'GET /api/co...00e1"\r\n\r\n'> cb=[IOLoop.add_future..() at C:\Users\Owner\AppData\Roaming\MLJAR-Studio\miniconda\lib\site-packages\tornado\ioloop.py:688]> while another task <Task pending name='Task-354' coro=<MultiKernelManager._async_start_kernel() running at C:\Users\Owner\AppData\Roaming\MLJAR-Studio\miniconda\lib\site-packages\jupyter_client\multikernelmanager.py:186>> is being executed.