search

microsoft / pylance-release

Documentation and issues for Pylance
Creative Commons Attribution 4.0 International
1.71k stars 765 forks source link

Chained file crash #6169

Closed rchiodo closed 2 months ago

rchiodo commented 3 months ago 
          @otavio-silva's problem is this:

Error: Debug Failure. False expression: Chained file path undefined doesn't match cellFilePaths file:///home/azakun/Documents/Code/Python/notebooks/Stable%20Diffusion%20XL/StableDiffisionXL.ipynb.py#X14sdnNjb2RlLXJlbW90ZQ%3D%3D at _0x2ee97f (/home/azakun/.vscode-server/extensions/ms-python.vscode-pylance-2024.7.1/dist/server.bundle.js:1:888452) at /home/azakun/.vscode-server/extensions/ms-python.vscode-pylance-2024.7.1/dist/server.bundle.js:1:817188

Not likely the same issue as the original poster. I'll link a new bug.

Originally posted by @rchiodo in https://github.com/microsoft/pylance-release/issues/6154#issuecomment-2243338275

rchiodo commented 3 months ago

@otavio-silva, can you post a copy of your notebook?

otavio-silva commented 3 months ago

@otavio-silva, can you post a copy of your notebook?

Here: StableDiffisionXL.zip

heejaechang commented 3 months ago

@otavio-silva can I get some repro steps if possible? also, can I get Trace log as in the troubleshooting guide?

your previous log is info level log, so it doesn't contain any detail except the assert.

otavio-silva commented 3 months ago

@heejaechang after some investigation, I found out that this is related to the NO notebook document for 'file//*.ipynb' error and disabling the Continue extension seems to have solved it for now.

KacieKK commented 3 months ago

related to this? https://github.com/continuedev/continue/issues/1463

otavio-silva commented 3 months ago

related to this? continuedev/continue#1463

Yup, that one. After removing it, can't reproduce any related errors.

heejaechang commented 3 months ago

I think this could be also partly due of this - https://github.com/microsoft/pylance-release/issues/6178

github-actions[bot] commented 2 months ago

This issue has been closed automatically because it needs more information and has not had recent activity. If the issue still persists, please reopen with the information requested. Thanks.