microsoft / microsoft/vscode-remote-release
用VScode编辑python文件后,会导致文件无法在vscode中打开,但在其他编译器中可正常打开,但是会出现乱码。
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
我使用VScode编辑python文件后,会导致文件无法在vscode中打开,但在其他编译器中可正常打开,但是会出现乱码。
版本:x64 1.129.0
文件权限完全正常,如果一开始使用其他编译器修改文件没有任何问题,只有python文件才会出现该问题。
2026-07-16 10:11:33.323 [error] [窗口] Error: 无法读取文件'd:\workspace\read_thermal.py-master\read_thermal.py-master\flir_image_extractor.py' (NoPermissions (FileSystemError): 出现未知错误。有关详细信息,请参阅日志。)
at pde.restoreReadError (vscode-file://vscode-app/c:/Users/88551/AppData/Local/Programs/Microsoft%20VS%20Code/125df4672b/resources/app/out/vs/workbench/workbench.desktop.main.js:5177:92151)
at Object.error (vscode-file://vscode-app/c:/Users/88551/AppData/Local/Programs/Microsoft%20VS%20Code/125df4672b/resources/app/out/vs/workbench/workbench.desktop.main.js:5177:92310)
at Object.onError (vscode-file://vscode-app/c:/Users/88551/AppData/Local/Programs/Microsoft%20VS%20Code/125df4672b/resources/app/out/vs/workbench/workbench.desktop.main.js:434:96341)
at vscode-file://vscode-app/c:/Users/88551/AppData/Local/Programs/Microsoft%20VS%20Code/125df4672b/resources/app/out/vs/workbench/workbench.desktop.main.js:434:95524
at vscode-file://vscode-app/c:/Users/88551/AppData/Local/Programs/Microsoft%20VS%20Code/125df4672b/resources/app/out/vs/workbench/workbench.desktop.main.js:434:93678
at Array.forEach ()
at qdi.emitError (vscode-file://vscode-app/c:/Users/88551/AppData/Local/Programs/Microsoft%20VS%20Code/125df4672b/resources/app/out/vs/workbench/workbench.desktop.main.js:434:93667)
at qdi.error (vscode-file://vscode-app/c:/Users/88551/AppData/Local/Programs/Microsoft%20VS%20Code/125df4672b/resources/app/out/vs/workbench/workbench.desktop.main.js:434:93358)
at Vxe.value (vscode-file://vscode-app/c:/Users/88551/AppData/Local/Programs/Microsoft%20VS%20Code/125df4672b/resources/app/out/vs/workbench/workbench.desktop.main.js:5177:105266)
at D._deliver (vscode-file://vscode-app/c:/Users/88551/AppData/Local/Programs/Microsoft%20VS%20Code/125df4672b/resources/app/out/vs/workbench/workbench.desktop.main.js:433:3268)
at D.fire (vscode-file://vscode-app/c:/Users/88551/AppData/Local/Programs/Microsoft%20VS%20Code/125df4672b/resources/app/out/vs/workbench/workbench.desktop.main.js:433:3587)
at l (vscode-file://vscode-app/c:/Users/88551/AppData/Local/Programs/Microsoft%20VS%20Code/125df4672b/resources/app/out/vs/workbench/workbench.desktop.main.js:1076:651)
at GHt.onResponse (vscode-file://vscode-app/c:/Users/88551/AppData/Local/Programs/Microsoft%20VS%20Code/125df4672b/resources/app/out/vs/workbench/workbench.desktop.main.js:1076:1880)
at GHt.onBuffer (vscode-file://vscode-app/c:/Users/88551/AppData/Local/Programs/Microsoft%20VS%20Code/125df4672b/resources/app/out/vs/workbench/workbench.desktop.main.js:1076:1735)
at Vxe.value (vscode-file://vscode-app/c:/Users/88551/AppData/Local/Programs/Microsoft%20VS%20Code/125df4672b/resources/app/out/vs/workbench/workbench.desktop.main.js:1075:1635)
at D._deliver (vscode-file://vscode-app/c:/Users/88551/AppData/Local/Programs/Microsoft%20VS%20Code/125df4672b/resources/app/out/vs/workbench/workbench.desktop.main.js:433:3268)
at D._deliverQueue (vscode-file://vscode-app/c:/Users/88551/AppData/Local/Programs/Microsoft%20VS%20Code/125df4672b/resources/app/out/vs/workbench/workbench.desktop.main.js:433:3357)
at D.fire (vscode-file://vscode-app/c:/Users/88551/AppData/Local/Programs/Microsoft%20VS%20Code/125df4672b/resources/app/out/vs/workbench/workbench.desktop.main.js:433:3692)
at we (vscode-file://vscode-app/c:/Users/88551/AppData/Local/Programs/Microsoft%20VS%20Code/125df4672b/resources/app/out/vs/workbench/workbench.desktop.main.js:431:15324)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with the named flir_image_extractor.py file in VS Code x64 1.129.0, comparing it with another editor as described. Inspect the provided NoPermissions error and relevant logs, then narrow down whether the failure depends on the Python file, encoding, or remote-development context. Done means the file opens in VS Code without the reported error and its contents remain readable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, vscode
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100