-
-
Notifications
You must be signed in to change notification settings - Fork 91
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
Is indexing ever finished? #17
Comments
Perhaps the file count is not getting incremented on those warn files and then the promise to update the status text not resolved. Try adding those files to |
@bmewburn Same result, I increased
|
Does code completion etc still work after it appears to get stuck? |
@bmewburn Yes. |
On another smaller project it works:
Seems like it fails on large projects. |
Does your large project have ~18455 files? If so I suspect there's a read file error being thrown in a promise that is being ignored which would mean the indexing does actually finish but never acknowledged (eg the read count stays on 18454). Off topic, what's the completion/go to/search etc experience like with a project that size? I have only used the extension on smaller projects with around 3000 files. |
Looks like it has
It works most of the time, sometimes go to definition does not work, not sure if because of project size or sth else. If you want to try large project, you can try:
It has more then 15000 php files. |
There's been some improvements with the promise handling. Indexing should now always complete in v0.8.0 |
@bmewburn : I'm using version 0.8.8 but it still happens. |
This is my console output:
And status bar label indicates it's still indexing after several hours:
It this expected?
The text was updated successfully, but these errors were encountered: