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

Can't open files #226898

Closed
roblourens opened this issue Aug 27, 2024 · 10 comments
Closed

Can't open files #226898

roblourens opened this issue Aug 27, 2024 · 10 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug ESM Issues caused by our AMD => ESM work important Issue identified as high-priority verified Verification succeeded
Milestone

Comments

@roblourens
Copy link
Member

Testing #226399

This is on mac. When I try to open any file in any folder, I see this.

Image

Weirdly, I can't find anything interesting in any log. Here's the trace-level window output. I opend id.ts from the quick pick

2024-08-27 15:22:15.296 [trace] SearchService#search: 43ms
2024-08-27 15:22:15.296 [trace] QuickAccess fileSearch 45ms
2024-08-27 15:22:16.143 [trace] [text file model] resolve() - enter file:///Users/roblou/code/vscode/src/vs/base/node/id.ts
2024-08-27 15:22:16.144 [trace] [text file model] resolveFromFile() file:///Users/roblou/code/vscode/src/vs/base/node/id.ts
2024-08-27 15:22:16.171 [trace] [text file model] dispose() file:///Users/roblou/code/vscode/src/vs/base/node/id.ts
2024-08-27 15:22:16.171 [trace] [backup tracker] discarding backup file:///Users/roblou/code/vscode/src/vs/base/node/id.ts 
2024-08-27 15:22:16.171 [error] {"isTrusted":true}
2024-08-27 15:22:16.171 [trace] [History stack global-default]: notifyNavigation() (editor: file:///Users/roblou/code/vscode/src/vs/base/node/id.ts, event: <none>)
2024-08-27 15:22:16.171 [trace] [History stack global-default]: notifyNavigation() not ignoring (editor: file:///Users/roblou/code/vscode/src/vs/base/node/id.ts, event: <none>)
2024-08-27 15:22:16.171 [trace] [History stack global-default]: onNonSelectionAwareEditorNavigation() (editor: file:///Users/roblou/code/vscode/src/vs/base/node/id.ts, event: <none>)
2024-08-27 15:22:16.171 [trace] [History stack global-default]: add() (editor: file:///Users/roblou/code/vscode/src/vs/base/node/id.ts, event: <none>)
2024-08-27 15:22:16.171 [trace] [History stack global-default]: index: 1, navigating: false
- group: 0, editor: walkThrough://vscode_getting_started_page, selection: <none>
- group: 0, editor: file:///Users/roblou/code/vscode/src/vs/base/node/id.ts, selection: <none>
			
2024-08-27 15:22:16.173 [trace] [History stack global-default]: index: 0, navigating: false
- group: 0, editor: walkThrough://vscode_getting_started_page, selection: <none>
			
2024-08-27 15:22:16.711 [trace] CommandService#executeCommand _setContext
2024-08-27 15:22:16.741 [trace] CommandService#executeCommand _setContext
@roblourens
Copy link
Member Author

Works on Linux though!

@bpasero bpasero added this to the August 2024 milestone Aug 28, 2024
@bpasero bpasero added the info-needed Issue requires more information from poster label Aug 28, 2024
@bpasero
Copy link
Member

bpasero commented Aug 28, 2024

@roblourens does this reproduce from a fresh profile or fresh user data dir?

So you were never able to open any editor during testing exploration?

@bpasero bpasero added the ESM Issues caused by our AMD => ESM work label Aug 28, 2024
@roblourens
Copy link
Member Author

It works with a fresh user data dir, and a fresh profile. I'm pretty sure I installed it from scratch yesterday, but I did enable setting sync, and it probably synced ui state.

I did do the testing, I was assigned Linux and it worked there. I was just trying it on my mac too where I see this issue.

@roblourens
Copy link
Member Author

Happy to do some debugging if you can suggest a place to set a breakpoint, I don't know where to start. I either see the original error or this one

Image

@roblourens
Copy link
Member Author

Something about failing to load jschardet

Image

$Hq (workbench.desktop.main.js:186457)
guessEncodingByBuffer (workbench.desktop.main.js:186679)
$gF (workbench.desktop.main.js:186756)
u (workbench.desktop.main.js:186562)
onEnd (workbench.desktop.main.js:186603)
(anonymous) (workbench.desktop.main.js:25901)
(anonymous) (workbench.desktop.main.js:25750)
i (workbench.desktop.main.js:25750)
end (workbench.desktop.main.js:25733)
onEnd (workbench.desktop.main.js:25967)
(anonymous) (workbench.desktop.main.js:25901)
(anonymous) (workbench.desktop.main.js:25750)
i (workbench.desktop.main.js:25750)
end (workbench.desktop.main.js:25733)
(anonymous) (workbench.desktop.main.js:546914)
B (workbench.desktop.main.js:3644)
fire (workbench.desktop.main.js:3669)
l (workbench.desktop.main.js:220766)
t (workbench.desktop.main.js:220823)
s (workbench.desktop.main.js:220814)
(anonymous) (workbench.desktop.main.js:220658)
B (workbench.desktop.main.js:3644)
C (workbench.desktop.main.js:3653)
fire (workbench.desktop.main.js:3673)
Ue (workbench.desktop.main.js:3226)
emit (VM4 sandbox_bundle:2)
onMessage (VM4 sandbox_bundle:2)

@bpasero
Copy link
Member

bpasero commented Aug 28, 2024

@roblourens good digging, can you share your settings? Do you have encoding related settings?

@bpasero
Copy link
Member

bpasero commented Aug 28, 2024

Nevermind, I can reproduce!

@bpasero bpasero added bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority and removed info-needed Issue requires more information from poster labels Aug 28, 2024
bpasero added a commit that referenced this issue Aug 28, 2024
bpasero added a commit that referenced this issue Aug 28, 2024
@bpasero bpasero closed this as completed Aug 29, 2024
@lszomoru
Copy link
Member

@bpasero, is the an ESM exploration build that contains the fix that can be used to verify this?

@bpasero
Copy link
Member

bpasero commented Aug 29, 2024

Steps:

  • configure files.autoGuessEncoding to true
  • close all files
  • open any file from explorer, it should show the contents

@lszomoru lszomoru added the verified Verification succeeded label Aug 29, 2024
@vs-code-engineering vs-code-engineering bot locked and limited conversation to collaborators Oct 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug ESM Issues caused by our AMD => ESM work important Issue identified as high-priority verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

4 participants