Fuzzy search cannot index project about fuzzy-finder HOT 8 CLOSED

Hi @stdc105, thanks for the report :)

I am unable to reproduce this in 1.42.0.

However it would be helpful if you:

1. Confirm that you are on safe mode to make sure there are no conflicts
2. Try is to do the search on a simple/small project just for testing purposes to make sure it's not just an edge case.

from fuzzy-finder.

I tried to reproducing on both 1.42.0-stable and 1.43.0-beta on both Mac and Windows and they are both working fine and rapidly, even on relatively large projects.

So we will need more details on the reproduction steps.

• Specially when it comes of how you open your project or is it a workspace?
• You mentioned fuzzy search, did you mean fuzzy finder?
• Can you clarify what did you mean by "open file" on the second step of reproduction?
• Can you reproduce the bug when you use the command pallet ctrl + shift + p > type "fuzzy" > choose "Toggle File Finder" > type the [file name]
• You could also try a classic system reboot for your PC that might resolve hidden issues related to memory, cache, buffer, etc.
• If non of the above worked I would suggest taking a look at this amazing article by our community manager, that might help us reproduce this bug.

FYI, this issue belongs to https://github.com/atom/fuzzy-finder, so I am going to transfer the issue to the proper repo.

Thank you for your reply!
Sorry to use some inaccurate words when describing the issue. I'll take a look at the article and find out what other information I could help reproduce the bug.

I'll try to describe information I already have here, and update the issue description accordingly.

• For opening a project, I tried using CLI atom . or open with right click menu on folder (Open with Atom) or open from an existing atom window with empty default editor.
• For fuzzy search, I mean fuzzy finder. Buffer finder and Git Status finder work, but File finder not (and this is the issue). The open file means File finder. Sorry again for using inaccurate words.
• I can reproduce the bug when using ctrl-shift-p with Toggle File Finder. Same behavior as using ctrl-b or ctrl-t (Showing "Indexing project... 0")
• I already tried reboot twice, and also already tried safe mode after each reboot. Same behavior.

I'll also try to reproduce the problem using another computer tonight.

from fuzzy-finder.

Hi @stdc105, thanks for the report :)

I am unable to reproduce this in 1.42.0.

However it would be helpful if you:

1. Confirm that you are on safe mode to make sure there are no conflicts
2. Try is to do the search on a simple/small project just for testing purposes to make sure it's not just an edge case.

I have tried to index project on safe mode on a small project (a directory with only 4 python files). No luck. For additional information, I'm on Win10 1809. I also tried other fuzzy search (ctrl-shift-b, ctrl-b), seems to work. Only ctrl-b/ctrl-p is affected. Hope these would be useful!

from fuzzy-finder.

Hi @stdc105, thanks for the report :)
I am unable to reproduce this in 1.42.0.
However it would be helpful if you:

1. Confirm that you are on safe mode to make sure there are no conflicts
2. Try is to do the search on a simple/small project just for testing purposes to make sure it's not just an edge case.

I have tried to index project on safe mode on a small project (a directory with only 4 python files). No luck. For additional information, I'm on Win10 1809. I also tried other fuzzy search (ctrl-shift-b, ctrl-b), seems to work. Only ctrl-b/ctrl-p is affected. Hope these would be useful!

Thanks for the information, I was testing on Mac, let me try reproducing on Windows.

Meanwhile, if you could confirm:

1. That you've used both ctrl + p and ctrl + t to reproduce.
2. The last version you had the functionality working with the same shortcuts.

from fuzzy-finder.

Hi @stdc105, thanks for the report :)
I am unable to reproduce this in 1.42.0.
However it would be helpful if you:

1. Confirm that you are on safe mode to make sure there are no conflicts
2. Try is to do the search on a simple/small project just for testing purposes to make sure it's not just an edge case.

I have tried to index project on safe mode on a small project (a directory with only 4 python files). No luck. For additional information, I'm on Win10 1809. I also tried other fuzzy search (ctrl-shift-b, ctrl-b), seems to work. Only ctrl-b/ctrl-p is affected. Hope these would be useful!

Thanks for the information, I was testing on Mac, let me try reproducing on Windows.

Meanwhile, if you could confirm:

1. That you've used both ctrl + p and ctrl + t to reproduce.
2. The last version you had the functionality working with the same shortcuts.

1. Yes, neither ctrl-t nor ctrl-p works, they essentially produce the exact same prompt, and I did verify both.
2. Yes, I was using 1.41.1 this morning and last week and I've been using ctrl-p all the time.

from fuzzy-finder.

from fuzzy-finder.

I tried to reproducing on both 1.42.0-stable and 1.43.0-beta on both Mac and Windows and they are both working fine and rapidly, even on relatively large projects.

So we will need more details on the reproduction steps.

• Specially when it comes of how you open your project or is it a workspace?
• You mentioned fuzzy search, did you mean fuzzy finder?
• Can you clarify what did you mean by "open file" on the second step of reproduction?
• Can you reproduce the bug when you use the command pallet ctrl + shift + p > type "fuzzy" > choose "Toggle File Finder" > type the [file name]
• You could also try a classic system reboot for your PC that might resolve hidden issues related to memory, cache, buffer, etc.
• If non of the above worked I would suggest taking a look at this amazing article by our community manager, that might help us reproduce this bug.

FYI, this issue belongs to https://github.com/atom/fuzzy-finder, so I am going to transfer the issue to the proper repo.

from fuzzy-finder.

Sorry for the late update:
I have tried to reproduce the issue on my personal machine but it seems to be good. I have fully deleted all atom installation (including project cache) and reinstall atom, it seems the problem is solved. While upgrading from 1.42 to 1.43 there is no problem any more, so I am not really sure if there is anything wrong before I reinstalled all the data. Anyway, sorry for any inconveniences, and I'll close the issue for now.
Thank you for helping! At least I'll know how to better write a bug report next time.

from fuzzy-finder.