Open tara-marchand opened 8 years ago
This problem break fuzzy search on remote project.
This should be fixed in Atom 1.9.0-beta0 and above.
I am experiencing the same problem at Atom 1.9.0-beta0.
@vtambourine Ok, thanks for reporting back. Does the issue still occur in safe mode (atom --safe
)?
@50Wliu no, in safe mode no error of that kind. Error is occurring only if I connected to the remote host via Nuclide package.
@vtambourine Can you also report this to Nuclide? I'm not sure who's at fault here, so I'm going to reopen this issue in the meantime.
In Nuclide, when there are remote projects, the paths of those projects are actually URIs. An example of two projects (one local one remote) below:
> atom.project.getPaths()
[
"/Users/jonaldislarry/Nuclide",
"nuclide://our.jonaldislarry.sb.facebook.com/data/users/remote-nuclide",
]
My guess is that fuzzy-finder is making the assumption that these will just be normal OS paths, and there's some parsing trouble due to that
It looks like maybe here
https://github.com/atom/fuzzy-finder/blob/master/lib/path-loader.coffee#L12
there should be a filter on the atom.project.getPaths()
array with some validation function that would exclude these URI-style paths.
Thanks for the info @johnislarry.
Any updates?
Bump!
I'm on Atom 1.16.0 now, and problem still occurs.
On the other hand, problem occurs only when trying to search via Cmd + P
. Fuzzy search made via Nuclide package on Cmd + T
works well.
Still seeing this on remote projects. Any update? My versions: Atom: 1.18.0 Nuclide: 0.232.0 Client OS:Mac Osx Server OS (optional): Linux
Any updates?
[Enter steps to reproduce below:]
Atom Version: 1.8.0 System: Mac OS X 10.11.5 Thrown From: fuzzy-finder package, v1.0.5
Stack Trace
Uncaught Error: ENOENT: no such file or directory, lstat '/nuclide:'
Commands
Config
Installed Packages