search

microsoft / vscode-jupyter

VS Code Jupyter extension
https://marketplace.visualstudio.com/items?itemName=ms-toolsai.jupyter
MIT License
1.3k stars 293 forks source link

Notebook cell gets stuck in 'Pending' state #13349

Closed dobos closed 11 months ago

dobos commented 1 year ago

Applies To

What happened?

When I start a notebook with 'Run all' and I have to kill the kernel for some reason with the kill command from the terminal the notebook cells that haven't been executed can get stuck in the 'Pending' state (little clock icon). Even if I close the notebook and reopen it, I cannot execute these pending cells anymore unless I convert them to a markdown cell and back. It would be great if the pending flag was reset when the kernel dies or otherwise killed without using the vscode 'Interrupt' and 'Restart' buttons. I have to restart vscode for the 'Pending' flags to go away. This is a vscode issue, the underlying kernel runs just fine.

No entry in the Jupyter log when I try to execute a cell marked as pending, so apparently vscode doesn't even attempt to execute that cell.

VS Code Version

Version: 1.77.3 (system setup) Commit: 704ed70d4fd1c6bd6342c436f1ede30d1cff4710 Date: 2023-04-12T09:16:02.548Z Electron: 19.1.11 Chromium: 102.0.5005.196 Node.js: 16.14.2 V8: 10.2.154.26-electron.0 OS: Windows_NT x64 10.0.19045 Sandboxed: No

Jupyter Extension Version

v2023.3.1201040234

Jupyter logs

--

Coding Language and Runtime Version

No response

Language Extension Version (if applicable)

No response

Anaconda Version (if applicable)

No response

Running Jupyter locally or remotely?

Remote

roblourens commented 1 year ago

Do you know if it's expected that we clean up those executions already in this case @DonJayamanne?

DonJayamanne commented 1 year ago

expected that we clean up those executions already in this case @DonJayamanne?

Not sure what you mean. Jupyter extension will clean up all executions at its end, (when users abort execution) I'm not entirely sure how we can end up in a pending state.

However I would like to try and replicate this at my end, will give me an idea where the problem is (whether jupyter extension isn't properly setting up some state or not).

DonJayamanne commented 1 year ago

When I start a notebook with 'Run all' and I have to kill the kernel for some reason with the kill command from the terminal

When you say terminal, do you mean the VS Code termina? Are you launching a Jupyter Notebook app and then connecting to that using VS Code?

I'll try to repro this at my end as well, However in the mean time please could you share the following logs as that would help me identify how we end up in the state of limbo and then I can try to fix that.

dobos commented 1 year ago

When you say terminal, do you mean the VS Code termina?

Yes, the vscode terminal, from a linux remote SSH session. I could just start another SSH connection from outside vscode, the results would be the same.

Are you launching a Jupyter Notebook app and then connecting to that using VS Code?

No, I open the notebook from the file explorer in vscode and let vscode start up the kernel for the notebook.

I'll try to repro next week from the office. I was checking the jupyter log and what I noticed is that no command is sent to the jupyter kernel when the cell is stuck in the pending state. Changing the cell to markdown and back to code solved the issue and then I saw the command in the jupyter log.

mateusz91t commented 1 year ago

Same problem with the execution of n cell with local jupyter kernel after today's upgrade to

Version: 1.79.2 (system setup) Commit: 695af097c7bd098fbf017ce3ac85e09bbc5dda06 Date: 2023-06-14T08:57:04.379Z Electron: 22.5.7 Chromium: 108.0.5359.215 Node.js: 16.17.1 V8: 10.8.168.25-electron.0 OS: Windows_NT x64 10.0.19045

ipykernel == 6.21.2 Python == 3.9.7

In terminal ipython the same code works fine.

The execution of every next cell get stuck with long Pending cell status (min. 10 seconds for eg. declare an empty list) always after run a cell that contains the following code:

def split_list_to_n_elements_lists(list_to_split: list, elements_in_one_chunk: int) -> list[list]:
    return [list_to_split[x : x + elements_in_one_chunk] for x in range(0, len(list_to_split), elements_in_one_chunk)]

chunked_list_of_strings = split_list_to_n_elements_lists(list_of_strings, 30)

image

DonJayamanne commented 1 year ago

Please could you enable logging as follows:

mateusz91t commented 1 year ago

Hi @DonJayamanne , I've sent the output log as you said. Last 2 cell executions from the log are pending about 30 seconds, eg. time difference between 407 and 408 line in my log file. log_VSCode_cell_pending.log

mateusz91t commented 1 year ago

I've downgrade VSC to 1.78.2, but it does not solve the problem. o.O I've done a test with other IDE. I tried run the same project and notebook with the same venv in PyCharm and there is no issue.

mateusz91t commented 1 year ago

After 2 days it works fine on v. 1.78.2. I don't understand why - I didn't change the code, data still similar. Weird.

cvarrichio commented 1 year ago

I am also having the exact same problem.

mikkelti commented 1 year ago

Me too!

ihyo772 commented 1 year ago

me too... still i don't know why

dhtc commented 1 year ago

I've noticed that a significant amount of time is spent on Handle Execution of Cells xx for xxx.ipynb before receiving an Kernel acknowledged execution response. This seems to contribute to the overall lag. I don't experience this issue when using Jupyter in a web browser, which suggests that the problem isn't related to my network.

Servinjesus1 commented 1 year ago

This happens for me when debugging cells:

  1. Debug a cell
  2. Disconnect from debugger
  3. Try stopping cell or letting it run its course
  4. Stop button remains and execution never seems to end
  5. Realize that other cells can run fine - this cell's just stuck waiting for some sort of conclusionary signal or something.
  6. Interrupting (toolbar or cell execution button) does nothing
Alita4195 commented 1 year ago

Same in here, debugging forever, interrupting kernel does nothing, changing it to markdown does nothing...

DonJayamanne commented 1 year ago

@dhtc @ihyo772 @mikkelti @cvarrichio Are you debugging in Jupyter as well when you run into this issue?

dhtc commented 1 year ago

Greetings, @DonJayamanne! I have made a remarkable discovery. It appears that the root of the issue may be attributed to the Jupyter PowerToys extension. Upon disabling said extension, all concerns have been successfully rectified.

DonJayamanne commented 1 year ago

oh thank you, hopefully the others can also confirm that. @Servinjesus1 @ihyo772 @mikkelti @cvarrichio /cc

mateusz91t commented 1 year ago

Hello after a few moths later... The same issue with similar code. Please see the gif: more strings = longer time of cell pending. The same code runs without troubles in IPython console. Could someone reproduce it with the same code? fyi @DonJayamanne

2023-09-05_00h49_56

import pandas as pd
import numpy as np

def split_list_to_n_elements_lists(list_to_split, elements_in_one_chunk):
    return [list_to_split[x : x + elements_in_one_chunk] for x in range(0, len(list_to_split), elements_in_one_chunk)]

series_len = 200_000
series = pd.Series(range(series_len)).apply(lambda x: np.random.choice(["male", "female"]))
series

s = split_list_to_n_elements_lists(series, 10)

s

1
faraz-m-awan commented 1 year ago

Facing the very same issue. I have to reload VSC to make it work. After some time, it's starts showing "Pending" status to cell again. It's so frustrating specially when you're working with huge data. After loading the data, at some point, it starts doing again and I have to reload the VSC again. Not only that, sometimes its IntelliSense stops working too

hbsmith commented 1 year ago

Still having this issue. Can't run a single notebook cell. Even when I quit VSCode and restart.

DonJayamanne commented 1 year ago

Please could you enable logging as follows:

matthias-brucklacher commented 1 year ago

I have the same issue. I tried this @DonJayamanne

Please could you enable logging as follows:

* Open settings & go into `Jupyter->Logging`

* Change the value to `verbose`

* Reload VS Code,

* Attempt to repro the issue & then copy the output from the `Jupyter` output panel.

but since the cell gets stuck (pending) no outputs are printed:

image

The terminal also shows nothing related: image image

erwusht commented 1 year ago

A possible reason I guess for getting stuck in pending is that ipykernel needs to load large resources taken up by variables, which takes a lot of time. When I load large-memory variables in the ipykernel, the following command is stuck in pending. Waiting for a long time or restarting the ipykernel can resolve the problem in some extent. I have no idea whether ipykernel try to loading and exhibiting the variables we saved in the ipykernel, when the variables are getting tremendous huge, the pending is on.

Dose anyone get pending, when loading or saving for a large variables?

CNwangbin commented 1 year ago

I have occured same error in my new machine. The error occured after this notebook started several minutes. I must restarted this notebook to run my code, but the work I done will be lossed. Is there anyway to solve that? 09:54:42.325 [debug] Start cell 13 execution @ 1698630882325 (clear output) 09:54:42.325 [info] Kernel acknowledged execution of cell 13 @ 1698630882325 09:54:42.327 [info] End cell 13 execution @ 1698630882327, started @ 1698630882325, elapsed time = 0.002s 09:54:42.327 [debug] Cell 13 executed with state Success 09:54:55.893 [debug] Jupyter completion time: 8 09:55:16.793 [debug] Jupyter completion time: 8 09:55:19.147 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.147 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.148 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.148 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.148 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.149 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.149 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.149 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.150 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.150 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.150 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.150 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.150 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.151 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.152 [info] Dispose Kernel '~/DeepPhy/temp_view_mdeep_data.ipynb' associated with '~/DeepPhy/temp_view_mdeep_data.ipynb' 09:55:19.152 [debug] Cancel pending cells 09:55:19.153 [debug] Shutdown session bf400052-9a29-408d-8b48-b9e2a77ee7a8, .jvsc74a57bd0f5110f52a60a6c1db62be5edb271289c5daa946a6d769c90a6797357d782f3b1./opt/miniconda/envs/pytorch2.1/python./opt/miniconda/envs/pytorch2.1/python.-m#ipykernel_launcher - start called from Error: at xy.shutdown (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.9.1102792234/out/extension.node.js:24:123857) at xy.disposeAsync (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.9.1102792234/out/extension.node.js:24:123279) at ~/.vscode-server/extensions/ms-toolsai.jupyter-2023.9.1102792234/out/extension.node.js:17:236128 at Qg.dispose (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.9.1102792234/out/extension.node.js:17:236342) at pv.disposeOldKernel (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.9.1102792234/out/extension.node.js:17:228606) at pv. (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.9.1102792234/out/extension.node.js:17:226939) at c.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1902) at c.A (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1972) at c.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:2188) at Oc. (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.9.1102792234/out/extension.node.js:2:2352412) at c.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1902) at c.A (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1972) at c.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:2188) at t.$acceptDocumentAndEditorsDelta (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:128:94030) at i.S (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:135:10827) at i.Q (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:135:10593) at i.M (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:135:9683) at i.L (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:135:8901) at s.value (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:135:7565) at c.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1902) at c.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:2119) at g.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:96:14010) at s.value (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:154:7902) at c.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1902) at c.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:2119) at g.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:96:14010) at r.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:96:17075) at s.value (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:96:15527) at c.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1902) at c.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:2119) at s.acceptChunk (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:96:11784) at s.value (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:96:11071) at c.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1902) at c.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:2119) at c.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:151:19153) 09:55:19.154 [info] Dispose Kernel process 339866. 09:55:19.165 [debug] Kernel got disposed, hence there is no longer a kernel associated with ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.166 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.167 [debug] Cancel pending cells 09:55:19.167 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.167 [debug] Cancel pending cells 09:55:19.167 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.167 [debug] Cancel pending cells 09:55:19.167 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.167 [debug] Cancel pending cells 09:55:19.167 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.167 [debug] Cancel pending cells 09:55:19.167 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.167 [debug] Cancel pending cells 09:55:19.167 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.167 [debug] Cancel pending cells 09:55:19.167 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.167 [debug] Cancel pending cells 09:55:19.167 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.167 [debug] Cancel pending cells 09:55:19.167 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.167 [debug] Cancel pending cells 09:55:19.167 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.167 [debug] Cancel pending cells 09:55:19.167 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.167 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.167 [debug] Cancel pending cells 09:55:19.167 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.167 [debug] Cancel pending cells 09:55:19.167 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 09:55:19.168 [debug] Shutdown session bf400052-9a29-408d-8b48-b9e2a77ee7a8, .jvsc74a57bd0f5110f52a60a6c1db62be5edb271289c5daa946a6d769c90a6797357d782f3b1./opt/miniconda/envs/pytorch2.1/python./opt/miniconda/envs/pytorch2.1/python.-m#ipykernel_launcher - shutdown complete 09:55:19.171 [debug] Disposed Kernel process 339866. 09:55:19.181 [debug] KernelProcess Exited, Exit Code - undefined

DonJayamanne commented 1 year ago

but the work I done will be lossed. Is there anyway to solve that?

what do you mean by work will be lost? Are you saying that you cannot even save a notebook when you run into this issue!

DonJayamanne commented 1 year ago

Jupyter completion time: 8 09:55:19.147 [debug] Disposing request as the cell was deleted

based on the logs, you seem to have removed cells then execution was in progress When you do this, the execution will stop and that what is going on

CNwangbin commented 1 year ago

but the work I done will be lossed. Is there anyway to solve that?

what do you mean by work will be lost? Are you saying that you cannot even save a notebook when you run into this issue!

The mean is that whenever I rerun my notebook, I have to run the code from the first code cell, I have to do all the works.

CNwangbin commented 1 year ago

Jupyter completion time: 8 09:55:19.147 [debug] Disposing request as the cell was deleted

based on the logs, you seem to have removed cells then execution was in progress When you do this, the execution will stop and that what is going on

No, I just debug my code in a cell. For example, I run some cells, and I revised my code in the last cell. But when I try to run the last cell, this error will occur. This error always occurs when I revise my code in a cell for several minutes. I don't known wether there are some packages I missed installation, since the machine is a new machine. If any machine (packages) version information you need to track this bug, please contact me. Thanks for your quickly reply.

DonJayamanne commented 1 year ago

No, I just debug my code in a cell. For example, I run some cells, and I revised my code in the last cell.

Are you using the debug functionality? or when you say debug you mean thats your workflow and not using Python Debugger in notebook is that right.

CNwangbin commented 1 year ago

No, I just debug my code in a cell. For example, I run some cells, and I revised my code in the last cell.

Are you using the debug functionality? or when you say debug you mean thats your workflow and not using Python Debugger in notebook is that right.

The debug I said is just I am revising my code in the jupyter cell.

DonJayamanne commented 1 year ago

For example, I run some cells, and I revised my code in the last cell. But when I try to run the last cell, this error will occur.

got it But as part of your work flow, you seem to be also deleting cells, at least that’s what I can see from the logs By deleting, I mean you somehow remove a cell that is already running

can you try again and share the logs, perhaps I can see whether that happens again

CNwangbin commented 1 year ago

Ok, I try to reproduce this bug. The word 'logs' you said, in my concept, is in "output --> jupyter"？Just like I showed in the first time?

CNwangbin commented 1 year ago

For example, I run some cells, and I revised my code in the last cell. But when I try to run the last cell, this error will occur.

got it But as part of your work flow, you seem to be also deleting cells, at least that’s what I can see from the logs By deleting, I mean you somehow remove a cell that is already running

can you try again and share the logs, perhaps I can see whether that happens again

I run some cells. And I copy some code from other file, and this error occure again. I didn't delete any cell in this notebook. 15:39:26.963 [info] End cell 14 execution @ 1698651566963, started @ 1698651566960, elapsed time = 0.003s 15:39:26.964 [debug] Cell 14 executed with state Success 15:39:36.023 [info] Handle Execution of Cells 16 for ~/DeepPhy/temp_view_mdeep_data.ipynb 15:39:36.026 [debug] start the kernel, options.disableUI=false for ~/DeepPhy/temp_view_mdeep_data.ipynb 15:39:36.027 [debug] Execution Request Sent to Kernel for cell 16 15:39:36.068 [debug] Start cell 16 execution @ 1698651576068 (clear output) 15:39:36.068 [info] Kernel acknowledged execution of cell 16 @ 1698651576068 15:39:36.229 [info] End cell 16 execution @ 1698651576229, started @ 1698651576068, elapsed time = 0.161s 15:39:36.229 [warn] Cancel all remaining cells due to cancellation or failure in execution 15:39:36.229 [debug] Cancel pending cells 15:39:36.229 [debug] Cell 16 executed with state Error 15:40:01.564 [debug] notebook communications already initialized for editor ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.107 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.107 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.107 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.107 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.107 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.107 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.107 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.107 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.107 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.107 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.108 [debug] Disposing request as the cell was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.109 [info] Dispose Kernel '~/DeepPhy/temp_view_mdeep_data.ipynb' associated with '~/DeepPhy/temp_view_mdeep_data.ipynb' 15:40:06.109 [debug] Cancel pending cells 15:40:06.110 [debug] Shutdown session 1b58abc3-7fe7-47bc-b28a-1f06af44d51b, .jvsc74a57bd0f5110f52a60a6c1db62be5edb271289c5daa946a6d769c90a6797357d782f3b1./opt/miniconda/envs/pytorch2.1/python./opt/miniconda/envs/pytorch2.1/python.-m#ipykernel_launcher - start called from Error: at xy.shutdown (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.9.1102792234/out/extension.node.js:24:123857) at xy.disposeAsync (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.9.1102792234/out/extension.node.js:24:123279) at ~/.vscode-server/extensions/ms-toolsai.jupyter-2023.9.1102792234/out/extension.node.js:17:236128 at Qg.dispose (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.9.1102792234/out/extension.node.js:17:236342) at pv.disposeOldKernel (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.9.1102792234/out/extension.node.js:17:228606) at pv.<anonymous> (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.9.1102792234/out/extension.node.js:17:226939) at c.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1902) at c.A (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1972) at c.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:2188) at Oc.<anonymous> (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.9.1102792234/out/extension.node.js:2:2352412) at c.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1902) at c.A (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1972) at c.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:2188) at t.$acceptDocumentAndEditorsDelta (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:128:94030) at i.S (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:135:10827) at i.Q (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:135:10593) at i.M (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:135:9683) at i.L (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:135:8901) at s.value (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:135:7565) at c.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1902) at c.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:2119) at g.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:96:14010) at s.value (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:154:7902) at c.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1902) at c.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:2119) at g.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:96:14010) at r.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:96:17075) at s.value (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:96:15527) at c.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1902) at c.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:2119) at s.acceptChunk (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:96:11784) at s.value (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:96:11071) at c.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1902) at c.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:2119) at c.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:151:19153) 15:40:06.110 [info] Dispose Kernel process 416781. 15:40:06.134 [debug] Kernel got disposed, hence there is no longer a kernel associated with ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.135 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.135 [debug] Cancel pending cells 15:40:06.135 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.135 [debug] Cancel pending cells 15:40:06.135 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.135 [debug] Cancel pending cells 15:40:06.135 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.135 [debug] Cancel pending cells 15:40:06.135 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.135 [debug] Cancel pending cells 15:40:06.135 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.135 [debug] Cancel pending cells 15:40:06.135 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.135 [debug] Cancel pending cells 15:40:06.135 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.135 [debug] Cancel pending cells 15:40:06.135 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.135 [debug] Cancel pending cells 15:40:06.135 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.135 [debug] Cancel pending cells 15:40:06.135 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.135 [debug] Cancel pending cells 15:40:06.135 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.135 [debug] Cancel pending cells 15:40:06.135 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:40:06.136 [debug] Shutdown session 1b58abc3-7fe7-47bc-b28a-1f06af44d51b, .jvsc74a57bd0f5110f52a60a6c1db62be5edb271289c5daa946a6d769c90a6797357d782f3b1./opt/miniconda/envs/pytorch2.1/python./opt/miniconda/envs/pytorch2.1/python.-m#ipykernel_launcher - shutdown complete 15:40:06.140 [debug] Disposed Kernel process 416781. 15:40:06.156 [debug] KernelProcess Exited, Exit Code - undefined

fomalhautb commented 1 year ago

Same problem

fomalhautb commented 1 year ago

I think I have found a potential way to reproduce the problem, not sure if it is the same for everybody else: When you save the notebook while the cell is still running, the cell hangs.

DonJayamanne commented 1 year ago

ms-toolsai-jupyter-insiders.vsix.zip

MrVPlusOne commented 1 year ago

I think I have found a potential way to reproduce the problem, not sure if it is the same for everybody else: When you save the notebook while the cell is still running, the cell hangs.

I'm having a similar issue in the past few days, and I noticed that the issue can happen right after I save the notebook. The language server will stop working (and I can see that the syntax coloring in the cells suddenly changes, and the jump-to-definition stops working, etc.) After this happens, running any notebook cell will hang and show the clock icon forever. The only fix I've found so far is to reload the notebook.

DonJayamanne commented 1 year ago

@MrVPlusOne can you try disabling or uninstalling pylance extension

@rebornix /cc

CNwangbin commented 1 year ago

ms-toolsai-jupyter-insiders.vsix.zip

  • Please download the above file
  • Extract it
  • Open the command palette in VS Code and select Install from VSIX
  • Select the above extracted vsix
  • When prompted, plese reload vscode
  • Replicate the issue once again
  • Please provide the logs once again

I done the above steps as you said. There are info I get, please check it. 14:56:21.769 [debug] Cell 16 executed with state Success 14:58:13.991 [info] Handle Execution of Cells 16 for ~/DeepPhy/temp_view_mdeep_data.ipynb 14:58:13.993 [debug] start the kernel, options.disableUI=false for ~/DeepPhy/temp_view_mdeep_data.ipynb 14:58:13.994 [debug] Execution Request Sent to Kernel for cell 16 14:58:14.002 [debug] Start cell 16 execution @ 1698821894002 (clear output) 14:58:14.002 [info] Kernel acknowledged execution of cell 16 @ 1698821894002 14:58:14.113 [info] End cell 16 execution @ 1698821894113, started @ 1698821894002, elapsed time = 0.111s 14:58:14.113 [debug] Cell 16 executed with state Success 14:58:34.792 [debug] Jupyter completion time: 9 14:58:35.523 [debug] Jupyter completion time: 8 14:58:35.657 [debug] Jupyter completion time: 9 14:58:36.055 [debug] Jupyter completion time: 9 14:58:36.728 [debug] Jupyter completion time: 8 14:58:39.138 [debug] Jupyter completion time: 20 14:58:39.430 [debug] Jupyter completion time: 8 14:58:41.739 [debug] Jupyter completion time: 8 14:58:41.889 [debug] Jupyter completion time: 8 14:58:42.085 [debug] Jupyter completion time: 9 14:58:42.262 [debug] Jupyter completion time: 10 14:58:45.314 [info] Handle Execution of Cells 16 for ~/DeepPhy/temp_view_mdeep_data.ipynb 14:58:45.318 [debug] start the kernel, options.disableUI=false for ~/DeepPhy/temp_view_mdeep_data.ipynb 14:58:45.319 [debug] Execution Request Sent to Kernel for cell 16 14:58:45.326 [debug] Start cell 16 execution @ 1698821925326 (clear output) 14:58:45.326 [info] Kernel acknowledged execution of cell 16 @ 1698821925326 14:58:45.490 [info] End cell 16 execution @ 1698821925490, started @ 1698821925326, elapsed time = 0.164s 14:58:45.490 [debug] Cell 16 executed with state Success 14:59:48.392 [info] Disposing request as the cell (-1) was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 14:59:48.602 [info] Disposing request as the cell (-1) was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 14:59:48.800 [info] Disposing request as the cell (-1) was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 14:59:49.168 [info] Disposing request as the cell (-1) was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 14:59:49.418 [info] Disposing request as the cell (-1) was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 14:59:49.602 [info] Disposing request as the cell (-1) was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 14:59:49.973 [info] Disposing request as the cell (-1) was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 14:59:50.192 [info] Disposing request as the cell (-1) was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 14:59:50.358 [info] Disposing request as the cell (-1) was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 14:59:50.629 [info] Disposing request as the cell (-1) was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 14:59:50.629 [info] Disposing request as the cell (-1) was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 14:59:50.629 [info] Disposing request as the cell (-1) was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 14:59:50.629 [info] Disposing request as the cell (-1) was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 14:59:50.629 [info] Disposing request as the cell (-1) was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 14:59:50.629 [info] Disposing request as the cell (-1) was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:01.256 [debug] Jupyter completion time: 9 15:00:05.152 [debug] Jupyter completion time: 7 15:00:11.117 [debug] Jupyter completion time: 5 15:00:11.213 [debug] Jupyter completion time: 9 15:00:11.380 [debug] Jupyter completion time: 8 15:00:12.710 [debug] Jupyter completion time: 8 15:00:12.803 [debug] Jupyter completion time: 8 15:00:12.956 [debug] Jupyter completion time: 8 15:00:13.052 [debug] Jupyter completion time: 7 15:00:31.184 [debug] Jupyter completion time: 4 15:00:33.356 [debug] Jupyter completion time: 9 15:00:51.832 [info] Disposing request as the cell (1) was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:51.832 [info] Disposing request as the cell (2) was deleted ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:51.833 [debug] Disposing kernel associated with ~/DeepPhy/temp_view_mdeep_data.ipynb, isClosed=true 15:00:51.833 [info] Dispose Kernel '~/DeepPhy/temp_view_mdeep_data.ipynb' associated with '~/DeepPhy/temp_view_mdeep_data.ipynb' 15:00:51.833 [debug] Cancel pending cells 15:00:51.835 [debug] Shutdown session 25e79c47-ba81-4f6a-b608-396178d90a19, .jvsc74a57bd0f5110f52a60a6c1db62be5edb271289c5daa946a6d769c90a6797357d782f3b1./opt/miniconda/envs/pytorch2.1/python./opt/miniconda/envs/pytorch2.1/python.-m#ipykernel_launcher - start called from Error: at hT.shutdown (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.11.100/dist/extension.node.js:256:3409) at hT.disposeAsync (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.11.100/dist/extension.node.js:256:2887) at e (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.11.100/dist/extension.node.js:232:27399) at WD.dispose (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.11.100/dist/extension.node.js:232:27633) at Zv.disposeOldKernel (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.11.100/dist/extension.node.js:232:18994) at Zv.<anonymous> (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.11.100/dist/extension.node.js:232:17214) at c.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1902) at c.A (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1972) at c.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:2188) at Gp.<anonymous> (~/.vscode-server/extensions/ms-toolsai.jupyter-2023.11.100/dist/extension.node.js:138:1258) at c.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1902) at c.A (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1972) at c.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:2188) at t.$acceptDocumentAndEditorsDelta (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:128:94030) at i.S (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:135:10827) at i.Q (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:135:10593) at i.M (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:135:9683) at i.L (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:135:8901) at s.value (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:135:7565) at c.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1902) at c.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:2119) at g.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:96:14010) at s.value (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:154:7902) at c.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1902) at c.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:2119) at g.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:96:14010) at r.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:96:17075) at s.value (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:96:15527) at c.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1902) at c.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:2119) at s.acceptChunk (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:96:11784) at s.value (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:96:11071) at c.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:1902) at c.fire (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:80:2119) at c.z (~/.vscode-server/bin/f1b07bd25dfad64b0167beb15359ae573aecd2cc/out/vs/workbench/api/node/extensionHostProcess.js:151:19153) 15:00:51.836 [info] Dispose Kernel process 527724. 15:00:51.854 [debug] Kernel got disposed, hence there is no longer a kernel associated with ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:51.855 [debug] Notebook document ~/DeepPhy/temp_view_mdeep_data.ipynb got closed 15:00:51.855 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:51.855 [debug] Cancel pending cells 15:00:51.855 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:51.855 [debug] Cancel pending cells 15:00:51.855 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:51.855 [debug] Cancel pending cells 15:00:51.855 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:51.855 [debug] Cancel pending cells 15:00:51.855 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:51.855 [debug] Cancel pending cells 15:00:51.855 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:51.855 [debug] Cancel pending cells 15:00:51.855 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:51.855 [debug] Cancel pending cells 15:00:51.855 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:51.855 [debug] Cancel pending cells 15:00:51.855 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:51.855 [debug] Cancel pending cells 15:00:51.855 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:51.855 [debug] Cancel pending cells 15:00:51.855 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:51.855 [debug] Cancel pending cells 15:00:51.855 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:51.855 [debug] Cancel pending cells 15:00:51.855 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:51.855 [debug] Cancel pending cells 15:00:51.855 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:51.855 [debug] Cancel pending cells 15:00:51.855 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:51.855 [debug] Cancel pending cells 15:00:51.855 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:51.855 [debug] Cancel pending cells 15:00:51.855 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:51.855 [debug] Cancel pending cells 15:00:51.855 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:51.855 [debug] Cancel pending cells 15:00:51.855 [debug] Cancel executions after closing notebook ~/DeepPhy/temp_view_mdeep_data.ipynb 15:00:51.856 [debug] Shutdown session 25e79c47-ba81-4f6a-b608-396178d90a19, .jvsc74a57bd0f5110f52a60a6c1db62be5edb271289c5daa946a6d769c90a6797357d782f3b1./opt/miniconda/envs/pytorch2.1/python./opt/miniconda/envs/pytorch2.1/python.-m#ipykernel_launcher - shutdown complete 15:00:51.861 [debug] Disposed Kernel process 527724. 15:00:51.899 [debug] KernelProcess Exited, Exit Code - undefined

DonJayamanne commented 1 year ago

@CNwangbin Thank you very much for the logs, very useful While executing cells from ‘. temp_view_mdeep_data.ipynb’ Did you at any point

Did you happen to disable all extensions?

based on the logs cells were deleted and the notebook was closed

CNwangbin commented 1 year ago

@CNwangbin Thank you very much for the logs, very useful While executing cells from ‘. temp_view_mdeep_data.ipynb’ Did you at any point

  • delete any cells
  • Or close this notebook

Did you happen to disable all extensions?

based on the logs cells were deleted and the notebook was closed

No, I didn't do any operation of them. I think it may caused by pylance. I will try to disable pylance extention and continue my work. If that is true or not true, I will report at there soon.

alethere commented 1 year ago

Had the same issue here, ended up realizing that the problem came from Pylance: https://github.com/microsoft/pylance-release/issues/5019

To solve it downgrade the Pylance of Vscode to 2023.10.4 Seems to work for now.

DonJayamanne commented 1 year ago

@alethere @CNwangbin What versions of Python extension and VS Code do you have installed?

CNwangbin commented 1 year ago

@alethere @CNwangbin What versions of Python extension and VS Code do you have installed?

The version of Python extension if v2023.20.0. The VS-code in my computer (Client end) is Version: 1.83.1 (user setup) Commit: f1b07bd25dfad64b0167beb15359ae573aecd2cc Date: 2023-10-10T23:48:05.904Z Electron: 25.8.4 ElectronBuildId: 24154031 Chromium: 114.0.5735.289 Node.js: 18.15.0 V8: 11.4.183.29-electron.0 OS: Windows_NT x64 10.0.19045 I don't know how to display the vscode-server on my Linux machine.

DonJayamanne commented 1 year ago

@CNwangbin Did downgrading or disabling the Pylance extension work?

CNwangbin commented 1 year ago

@CNwangbin Did downgrading or disabling the Pylance extension work?

I am trying to do this. Report you later.

DonJayamanne commented 1 year ago

Did downgrading or disabling the Pylance extension work?

If you have Ruff or similar python extensions, please consider disabling those as well. Basically disable all except

As I suspect this issue is caused by some other extension.

CNwangbin commented 1 year ago

Did downgrading or disabling the Pylance extension work?

If you have Ruff or similar python extensions, please consider disabling those as well. Basically disable all except

  • Python
  • Jupyter
  • Notebook Renderers

As I suspect this issue is caused by some other extension.

No, I only have extensions Python, Jupyter, GitHub Copliot, Pylance. Now, I think Pylance maybe is the reason.

DonJayamanne commented 1 year ago

Now, I think Pylance maybe is the reason.

Please keep using Jupyter withoupyt Pylance for a while, until you feel confident that it has not reproduced at all for long enough.

Thanks again.