Kernel crashed when trigger intelligence

[eromoe]

Environment data

• VS Code version: 1.88.1
• Jupyter Extension version (available under the Extensions sidebar): latest
• Python Extension version (available under the Extensions sidebar): latest
• OS (Windows | Mac | Linux distro) and version: win10
• Python and/or Anaconda version: 3.10
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
• Jupyter server running: Local | Remote | N/A

Actual behaviour

Once I type . after pd.Series(np.arange(10)) crashed. Happen on one of my env .

gif :

Logs

``` 11:21:14.261 [error] Disposing session as kernel process died ExitCode: 3221225725, Reason: 11:21:14.326 [info] Cell 72 completed in -1713669671.051s (start: 1713669671051, end: undefined) ```

And it print another error after I click restart

1:29:29.589 [error] Error in waiting for code ms-toolsai.jupyter-252 to complete [Error: Canceled future for execute_request message before replies were done
	at oi.dispose (~\.vscode\extensions\ms-toolsai.jupyter-2024.3.1-win32-x64\dist\node_modules\@jupyterlab\services\lib\kernel\nonSerializingKernel.js:11:22379)
	at ~\.vscode\extensions\ms-toolsai.jupyter-2024.3.1-win32-x64\dist\node_modules\@jupyterlab\services\lib\kernel\nonSerializingKernel.js:11:93953
	at Map.forEach (<anonymous>)
	at n._clearKernelState (~\.vscode\extensions\ms-toolsai.jupyter-2024.3.1-win32-x64\dist\node_modules\@jupyterlab\services\lib\kernel\nonSerializingKernel.js:11:93939)
	at n.dispose (~\.vscode\extensions\ms-toolsai.jupyter-2024.3.1-win32-x64\dist\node_modules\@jupyterlab\services\lib\kernel\nonSerializingKernel.js:11:87407)
	at ~\.vscode\extensions\ms-toolsai.jupyter-2024.3.1-win32-x64\dist\extension.node.js:342:13256
	at On (~\.vscode\extensions\ms-toolsai.jupyter-2024.3.1-win32-x64\dist\extension.node.js:77:9941)
	at CT.start (~\.vscode\extensions\ms-toolsai.jupyter-2024.3.1-win32-x64\dist\extension.node.js:342:13232)
	at CT.restart (~\.vscode\extensions\ms-toolsai.jupyter-2024.3.1-win32-x64\dist\extension.node.js:342:13013)
	at gT.restart (~\.vscode\extensions\ms-toolsai.jupyter-2024.3.1-win32-x64\dist\extension.node.js:312:30487)
	at V_.restart (~\.vscode\extensions\ms-toolsai.jupyter-2024.3.1-win32-x64\dist\extension.node.js:315:32146)
	at async r.wrapKernelMethodImpl (~\.vscode\extensions\ms-toolsai.jupyter-2024.3.1-win32-x64\dist\extension.node.js:343:56464)]
11:29:30.535 [info] Process Execution: c:\envs\quant\python.exe -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
11:29:30.539 [info] Process Execution: c:\envs\quant\python.exe -m ipykernel_launcher --f=~\AppData\Roaming\jupyter\runtime\kernel-v2-23844r6kxsHWsY8Uo.json

[eromoe]

Looks like only . after pd.Series()/pd.Dataframe() trigger this crash.

x = pd.Series(np.arange(10))
x.  # ( this dot doesn't trigger)

pd.Series(np.arange(10)).  # ( this dot triggers)

Reinstall packages with no help

pip uninstall numpy scipy numba pandas
mamba install numpy==1.24.4 scipy numba==0.57.1 pandas==1.5.3 --force-reinstall -y

[DonJayamanne]

Thank you for filing this issue and sorry you are running into this. Please can you disable the following setting and see if that makes a difference?

[eromoe]

@DonJayamanne I can't see the image .

[RodolfoFigueroa]

Looks like only . after pd.Series()/pd.Dataframe() trigger this crash.

Can confirm this specific pattern is the culprit. Incidentally, it also happens with a geopandas GeoDataFrame/GeoSeries.

[DonJayamanne]

@eromoe sorry I missed you message. @RodolfoFigueroa Does it work if you disable the setting Enable Kernel Completions

[eromoe]

@DonJayamanne Yes, disable that avoid the crash.

[DonJayamanne]

@eromoe Please can you try the following:

• Create a new python environment
• Install the packages into that new environment
• Enable kernel completions from the settings Check whether the kernel crashes again for you.

[vs-code-engineering[bot]]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

[vs-code-engineering[bot]]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!