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.

Sign up for GitHub

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

Jump to bottom

TypeError: Cannot read property 'verboseLogging' of undefined #4534

Closed
mysticatea opened this issue Mar 22, 2016 · 7 comments
Closed

TypeError: Cannot read property 'verboseLogging' of undefined #4534

mysticatea opened this issue Mar 22, 2016 · 7 comments
Assignees
@isidorn
Labels
candidate Issue identified as probable candidate for fixing in the next release important Issue identified as high-priority verified Verification succeeded
Milestone
March 2016

Comments

@mysticatea
Copy link

  • VSCode Version:
    • Version: 0.10.12-insider
    • Commit: ef2a1fc
    • Date: 2016-03-21T11:33:38.240Z
    • Shell: 0.35.6
    • Renderer: 45.0.2454.85
    • Node: 4.1.1
  • OS Version: Windows 7 64bit

Steps to Reproduce:

  1. I opened a folder.
    It's 100% reproduced on the folder. But it's not reproduced on another folder. I'm not sure what actual conditions are.

As a result of this error, the explorer area shows nothing.

image
image
@bpasero
Copy link
Member

bpasero commented Mar 22, 2016

@mysticatea would you be able to share this folder with me?

@bpasero bpasero added important Issue identified as high-priority bug Issue identified by VS Code Team member as probable bug labels Mar 22, 2016
@bpasero bpasero added this to the March 2016 milestone Mar 22, 2016
@bpasero bpasero self-assigned this Mar 22, 2016
@bpasero
Copy link
Member

bpasero commented Mar 22, 2016

Found the issue: https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/services/files/node/fileService.ts#L709

@mysticatea
Copy link
Author

Thank you!

I'm sorry, I cannot share that folder since some reasons.
But fortunately, after I modified fileService.ts#L709 with $this (f in minified code), this issue was fixed.

VSCode seemed to try to open a removed junction folder (I had opened the folder before) when it was running on fileService.ts#L709.

@bpasero
Copy link
Member

bpasero commented Mar 22, 2016

Thanks, we can fix this without further help. For now you will have to use the stable version at least on that folder.

@DickvdBrink
Copy link
Contributor

Same issue here; on all my workspaces.
Is this issue there for a lot of people? Might want to create a new insider build if that is the case to get feedback.
edit a fixed it - guess it is not a really common issue.

@bpasero bpasero mentioned this issue Mar 22, 2016
Merged
@bpasero bpasero added candidate Issue identified as probable candidate for fixing in the next release and removed stable-candiate labels Mar 22, 2016
@bpasero bpasero removed the bug Issue identified by VS Code Team member as probable bug label Mar 23, 2016
@bpasero bpasero assigned isidorn and unassigned bpasero Mar 23, 2016
@bpasero
Copy link
Member

bpasero commented Mar 23, 2016

To verify, open a folder on Windows with permission denied error and verify that those with permission errors simply do not show up but do not cause other things to show in the explorer.

@isidorn
Copy link
Contributor

isidorn commented Mar 23, 2016

Verified by opening C:\users, folders like administrator are simply not shown and other look fine

@isidorn isidorn added the verified Verification succeeded label Mar 23, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@isidorn isidorn

Labels
candidate Issue identified as probable candidate for fixing in the next release important Issue identified as high-priority verified Verification succeeded
Projects
None yet
Milestone
March 2016
Development

No branches or pull requests
4 participants
@DickvdBrink @bpasero @isidorn @mysticatea