Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash in pylance when using 'editable' install setting #6987

Closed
rchiodo opened this issue Feb 25, 2025 · 1 comment
Closed

Crash in pylance when using 'editable' install setting #6987

rchiodo opened this issue Feb 25, 2025 · 1 comment
Assignees
Labels
fixed in next version (release) A fix has been implemented and will appear in an upcoming version needs repro Issue has not been reproduced yet

Comments

@rchiodo
Copy link
Contributor

rchiodo commented Feb 25, 2025

Not sure why the wasm file isn't being downloaded, but this shouldn't crash the server:

2025-02-25 11:21:53.034 [info] Error: ENOENT: no such file or directory, open 'c:\Users\luabud\.vscode-insiders\extensions\ms-python.vscode-pylance-2025.2.101\dist\wasi\python-3.13.2\python.wasm'
    at Object.openSync (node:fs:575:18)
    at Object.func [as openSync] (node:electron/js2c/node_init:2:2559)
    at Object.readFileSync (node:fs:454:35)
    at Object.t.readFileSync (node:electron/js2c/node_init:2:10175)
    at n.readFileSync (c:\Users\luabud\.vscode-insiders\extensions\ms-python.vscode-pylance-2025.2.101\dist\vendor.bundle.js:2:1010001)
    at c:\Users\luabud\.vscode-insiders\extensions\ms-python.vscode-pylance-2025.2.101\dist\vendor.bundle.js:2:1057272
    at w.makeCallSync (c:\Users\luabud\.vscode-insiders\extensions\ms-python.vscode-pylance-2025.2.101\dist\vendor.bundle.js:2:1059368)
    at w.readFileSync (c:\Users\luabud\.vscode-insiders\extensions\ms-python.vscode-pylance-2025.2.101\dist\vendor.bundle.js:2:1057240)
    at d.readFileSync (c:\Users\luabud\.vscode-insiders\extensions\ms-python.vscode-pylance-2025.2.101\dist\vendor.bundle.js:2:1017360)
    at S.readFileSync (c:\Users\luabud\.vscode-insiders\extensions\ms-python.vscode-pylance-2025.2.101\dist\vendor.bundle.js:2:1017360)
    at x.readFileSync (c:\Users\luabud\.vscode-insiders\extensions\ms-python.vscode-pylance-2025.2.101\dist\pyright.bundle.js:1:1202973)
    at readFileSync (c:\Users\luabud\.vscode-insiders\extensions\ms-python.vscode-pylance-2025.2.101\dist\pyright.bundle.js:1:1584541)
    at _0x4f99d9.readFileSync (c:\Users\luabud\.vscode-insiders\extensions\ms-python.vscode-pylance-2025.2.101\dist\server.bundle.js:1:721423)
    at new _0x1c86c6 (c:\Users\luabud\.vscode-insiders\extensions\ms-python.vscode-pylance-2025.2.101\dist\server.bundle.js:1:666782)
    at _0x1d1ae6._createSandbox (c:\Users\luabud\.vscode-insiders\extensions\ms-python.vscode-pylance-2025.2.101\dist\server.bundle.js:1:670909)
    at _0x1d1ae6.getSandbox (c:\Users\luabud\.vscode-insiders\extensions\ms-python.vscode-pylance-2025.2.101\dist\server.bundle.js:1:670554)
    at _0x230b6b._cachePthPaths (c:\Users\luabud\.vscode-insiders\extensions\ms-python.vscode-pylance-2025.2.101\dist\server.bundle.js:1:1195434)
@rchiodo rchiodo self-assigned this Feb 25, 2025
@github-actions github-actions bot added the needs repro Issue has not been reproduced yet label Feb 25, 2025
@bschnurr bschnurr added the fixed in next version (main) A fix has been implemented and will appear in an upcoming version label Feb 25, 2025
@debonte debonte added fixed in next version (release) A fix has been implemented and will appear in an upcoming version and removed fixed in next version (main) A fix has been implemented and will appear in an upcoming version labels Feb 26, 2025
@debonte
Copy link
Contributor

debonte commented Feb 27, 2025

This issue has been fixed in prerelease version 2025.2.102, which we've just released. You can find the changelog here: CHANGELOG.md

@debonte debonte closed this as completed Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixed in next version (release) A fix has been implemented and will appear in an upcoming version needs repro Issue has not been reproduced yet
Projects
None yet
Development

No branches or pull requests

4 participants