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

After installing the extension, load project is always displayed in the status bar #2554

Closed
Uomfan opened this issue Dec 11, 2020 · 22 comments
Closed
Labels

Comments

@Uomfan
Copy link

Uomfan commented Dec 11, 2020

Issue Type: Bug

After installing the extension, load project is always displayed in the status bar

Extension version: 0.31.1
VS Code version: Code 1.51.1 (e5a624b788d92b8d34d1392e4c4d9789406efe8f, 2020-11-10T23:34:32.027Z)
OS version: Windows_NT x64 10.0.18363

System Info
Item Value
CPUs Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz (6 x 2904)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
opengl: enabled_on
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 15.92GB (10.88GB free)
Process Argv --crash-reporter-id 04a8e1df-e442-4b88-bfb4-8ec54bee657a
Screen Reader no
VM 0%
@yoyo930021
Copy link
Member

Where is your vetur.config.js?
Or what is folder path opened in VSCode?

@willhoyle
Copy link

I'm getting the same issue. The project loads forever. How can I debug this? I tried uninstalling/reinstalling but no luck.

@yoyo930021
Copy link
Member

I'm getting the same issue. The project loads forever. How can I debug this? I tried uninstalling/reinstalling but no luck.

Try to use Vetur: show doctor info command in vscode and post message in this issue.

@wokalek-work
Copy link

wokalek-work commented Dec 11, 2020

Same problem.

Infinite loading project from C:, but my project not in root of C disk.

image
image

@yoyo930021
Copy link
Member

yoyo930021 commented Dec 11, 2020

Same problem.

Infinite loading project from C:, but my project not in root of C disk.

image
image

If you have vetur.config.js?

Try to use Vetur: show doctor info command in vscode and post message in this issue.

@wokalek-work
Copy link

@yoyo930021

Output channel

image

Vetur: show doctor shows nothing.

vetur.config.js is default, I have not changed it

@yoyo930021
Copy link
Member

yoyo930021 commented Dec 11, 2020

@yoyo930021

Output channel

image

Vetur: show doctor shows nothing.

vetur.config.js is default, I have not changed it

What is content in vetur.config.js?
And what is folder path for opened ?

@wokalek-work
Copy link

@yoyo930021

And what is folder path for opened ?

C:\Users\wokalek\work\projects\volochanka\
C:\Users\wokalek\work\projects\optimize-village-images\

But I remove optimize-village-images and got this errors, which were not there before

image

@wokalek-work
Copy link

wokalek-work commented Dec 11, 2020

@yoyo930021

I do not have any vetur.config.js, my project on Nuxt.js.

@yoyo930021
Copy link
Member

yoyo930021 commented Dec 11, 2020

@yoyo930021

And what is folder path for opened ?

C:\Users\wokalek\work\projects\volochanka\
C:\Users\wokalek\work\projects\optimize-village-images\

But I remove optimize-village-images and got this errors, which were not there before

image

Is this warning correct?

I think we have some bug in windows.

@wokalek-work
Copy link

wokalek-work commented Dec 11, 2020

@yoyo930021 yes, I think, nuxt.js project (with node_modules) placed in volochanka/nuxt, not in root of project folder.

image

But I do not want to see this errors...

@yoyo930021
Copy link
Member

@yoyo930021 yes, I think, nuxt.js project (with node_modules) placed in volochanka/nuxt, not in root of project folder.

image

But I do not want to see this errors...

In your case, please keep package.json in opened project root.
Or add vetur.config.js in this project.

module.exports = {
  projects: ['./nuxt']
}

@wokalek-work
Copy link

@yoyo930021 thanks a lot!

Apparently this is not a problem from this issue, sorry

@yoyo930021
Copy link
Member

@yoyo930021 thanks a lot!

Apparently this is not a problem from this issue, sorry

No problem.
Our documentation and warnings need to be improved. 😅
I also find some bug about this case. Thanks your help.

In fact, this kind of project was also problematic before.
It's just that Vetur doesn't give any errors or warnings.

@yoyo930021
Copy link
Member

Fixed in 1f444d3

@willhoyle
Copy link

willhoyle commented Dec 11, 2020

Ok I've narrowed it down a bit.
rolling back to v0.30.3 works so it must be a changed introduced in v0.31.0.

By the way, I've never had a vetur.config.js file and it has always worked, not sure if that is undefined behaviour to omit this file.

v0.31.0 (and v0.31.1) outputs an error:

Error: EACCES: permission denied, scandir '/home/will/projects/dashboard/data/postgres'
    at Object.readdirSync (fs.js:854:3)
    at Object.fs.readdirSync (electron/js2c/asar.js:621:39)
    at readdirWithFileTypes (/home/will/.vscode/extensions/octref.vetur-0.31.1/server/dist/vls.js:34:39846)
    at Object.read (/home/will/.vscode/extensions/octref.vetur-0.31.1/server/dist/vls.js:34:39776)
    at JL.scandirSync [as _scandir] (/home/will/.vscode/extensions/octref.vetur-0.31.1/server/dist/vls.js:34:41945)
    at JL._handleDirectory (/home/will/.vscode/extensions/octref.vetur-0.31.1/server/dist/vls.js:34:47863)
    at JL._handleQueue (/home/will/.vscode/extensions/octref.vetur-0.31.1/server/dist/vls.js:34:47789)
    at JL.read (/home/will/.vscode/extensions/octref.vetur-0.31.1/server/dist/vls.js:34:47645)
    at QL.read (/home/will/.vscode/extensions/octref.vetur-0.31.1/server/dist/vls.js:34:48639)
    at AM.walkSync [as _walkSync] (/home/will/.vscode/extensions/octref.vetur-0.31.1/server/dist/vls.js:34:49920)

which makes sense because the folder permissions are as follows:

drwx------ 19 guest-lhspf4 will 4096 Dec 11 09:41 postgres (no group read access for will).

Should vetur catch this error and just ignore it? (or log it but continue scanning the directories?). By the way, this folder is in my .gitignore, should vetur ignore folders/files in .gitignore?

Happy to help in any other way, let me know!

@joaopauloufal
Copy link

joaopauloufal commented Dec 11, 2020

Ok I've narrowed it down a bit.
rolling back to v0.30.3 works so it must be a changed introduced in v0.31.0.

By the way, I've never had a vetur.config.js file and it has always worked, not sure if that is undefined behaviour to omit this file.

v0.31.0 (and v0.31.1) outputs an error:

Error: EACCES: permission denied, scandir '/home/will/projects/dashboard/data/postgres'
    at Object.readdirSync (fs.js:854:3)
    at Object.fs.readdirSync (electron/js2c/asar.js:621:39)
    at readdirWithFileTypes (/home/will/.vscode/extensions/octref.vetur-0.31.1/server/dist/vls.js:34:39846)
    at Object.read (/home/will/.vscode/extensions/octref.vetur-0.31.1/server/dist/vls.js:34:39776)
    at JL.scandirSync [as _scandir] (/home/will/.vscode/extensions/octref.vetur-0.31.1/server/dist/vls.js:34:41945)
    at JL._handleDirectory (/home/will/.vscode/extensions/octref.vetur-0.31.1/server/dist/vls.js:34:47863)
    at JL._handleQueue (/home/will/.vscode/extensions/octref.vetur-0.31.1/server/dist/vls.js:34:47789)
    at JL.read (/home/will/.vscode/extensions/octref.vetur-0.31.1/server/dist/vls.js:34:47645)
    at QL.read (/home/will/.vscode/extensions/octref.vetur-0.31.1/server/dist/vls.js:34:48639)
    at AM.walkSync [as _walkSync] (/home/will/.vscode/extensions/octref.vetur-0.31.1/server/dist/vls.js:34:49920)

which makes sense because the folder permissions are as follows:

drwx------ 19 guest-lhspf4 will 4096 Dec 11 09:41 postgres (no group read access for will).

Should vetur catch this error and just ignore it? (or log it but continue scanning the directories?). By the way, this folder is in my .gitignore, should vetur ignore folders/files in .gitignore?

Happy to help in any other way, let me know!

I also have this same problem. A suggestion for improvement would be that the vetur has some configuration to ignore certain folders.

Captura de tela de 2020-12-11 13-03-41

@yoyo930021
Copy link
Member

Fix and release in v0.31.2

@yoyo930021
Copy link
Member

@joaopauloufal @willhoyle
It could be other problems.
If you still have same error in v0.31.2, you can open a new issue.

@willhoyle
Copy link

Ok will do. It might be something else because v0.31.2 doesn't fix it. Thanks

@Nexulo
Copy link

Nexulo commented Feb 11, 2021

hello, unfortunately i also have this problem. for some time now it has been loading the project continuously as soon as i open the first vue file. this takes up quite a bit of my macbook's power and it also gets warmer than it should.

@yoyo930021
Copy link
Member

Please open a new issue.
Use issue template and provide more information like #2554 (comment)

@vuejs vuejs locked as resolved and limited conversation to collaborators Feb 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

6 participants