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

Network files not being found #9

Closed
NikoMuffin opened this issue Jun 6, 2021 · 16 comments
Closed

Network files not being found #9

NikoMuffin opened this issue Jun 6, 2021 · 16 comments
Labels
bug Something isn't working High Priority High Priority BUGS

Comments

@NikoMuffin
Copy link
Collaborator

Everything app is separately finding files in networked locations when FS is not.

Some more specifics:

  1. Mac Mini network share files & folders using SMB
  2. network folder is mapped to O:\ drive
  3. Adding O:\ drive or manual \ path doesn't pull all of the files
  4. Some of the files show, some don't.
  5. I have permissions for read/write to all of the files.
  6. Listary and flow launcher can access all of the files.
@NikoMuffin NikoMuffin added bug Something isn't working High Priority High Priority BUGS labels Jun 6, 2021
@NikoMuffin
Copy link
Collaborator Author

NikoMuffin commented Jun 6, 2021

Can anyone replicate this? @Nomad-0

EDIT: Confirmed in Issue #80

@Nomad-0
Copy link
Collaborator

Nomad-0 commented Jun 6, 2021

sorry, I don’t have network drives

@NikoMuffin
Copy link
Collaborator Author

NikoMuffin commented Jun 12, 2021

Can confirm this is still active in latest build
image

@kwanice
Copy link

kwanice commented Jun 12, 2021

yes, still very buggy... @Metroid-Prime
sometimes i can access some files, sometimes not, sometimes i have to wait 5 seconds or more for one result,
or i have to add a new character, or remove one to display some result..quite weird behavior :p

update : confirm, unfortunately files cant be found on my network folder..with listary it work fine...:'(

@adirh3
Copy link
Owner

adirh3 commented Jun 12, 2021

This issue has been potentially fixed in version 0.9.85.45

@NikoMuffin
Copy link
Collaborator Author

NikoMuffin commented Jun 13, 2021

Still broken in 0.9.85.45. Many network files not found

EDIT: Fresh copy of FS, can confirm definitely broken with O:\ or \192.168.1.29\Documents in the index path

@adirh3
Copy link
Owner

adirh3 commented Jun 13, 2021

Still broken in 0.9.85.45. Many network files not found

EDIT: Fresh copy of FS, can confirm definitely broken with O:\ or \192.168.1.29\Documents in the index path

I need more information, does it happen for all network drives? Files not found are in a specific directory or all files not found? Once network drive configured and you rebuild index, do you progress ring in Fluent Search?

@adirh3
Copy link
Owner

adirh3 commented Jun 14, 2021

This issue has been potentially fixed in version 0.9.85.50

@NikoMuffin
Copy link
Collaborator Author

Hi @adirh3
Apologies for the late reply. I will validate this tonight when I get back on my home computer!

@NikoMuffin
Copy link
Collaborator Author

NikoMuffin commented Jun 14, 2021

Still broken in 0.9.85.45. Many network files not found
EDIT: Fresh copy of FS, can confirm definitely broken with O:\ or \192.168.1.29\Documents in the index path

I need more information, does it happen for all network drives? Files not found are in a specific directory or all files not found? Once network drive configured and you rebuild index, do you progress ring in Fluent Search?

(EDIT: clarification for this message. I haven't validated the new version yet. Will do it tonight)
In the meantime, an explanation -- It's completely random, but I have a folder called /Documents. I tried adding both the network mapped drive O:\ and then also tried the manual network address \192.168.1.25*dirname* and rebuilt the index in FS. Tried exiting and re-opening and files aren't found.

@adirh3
Copy link
Owner

adirh3 commented Jun 14, 2021

This issue has been potentially fixed in version 0.9.85.55

@NikoMuffin
Copy link
Collaborator Author

NikoMuffin commented Jun 15, 2021

This issue has been potentially fixed in version 0.9.85.55

This was a longstanding issue and OMG I think you did it! Thank you @adir!

@nataloko
Copy link

nataloko commented Mar 7, 2022

New user here.
Finding this same problem on a brand new installation (0.9.90)

@adirh3
Copy link
Owner

adirh3 commented Mar 7, 2022

New user here. Finding this same problem on a brand new installation (0.9.90)

This should be working in 0.9.90, what kind of network drive do you have?
Not all drives are supported in 0.9.90, but in 0.9.91 all should work, you can try it out by changing the release feed to nightly in Settings -> System (note - it's less stable than 9.90)

@nataloko
Copy link

nataloko commented Mar 8, 2022

New user here. Finding this same problem on a brand new installation (0.9.90)

This should be working in 0.9.90, what kind of network drive do you have? Not all drives are supported in 0.9.90, but in 0.9.91 all should work, you can try it out by changing the release feed to nightly in Settings -> System (note - it's less stable than 9.90)

Hi. As far as I know is a standard Windows "shared folder". I tried both a mapped drive and direct access (\shared\folder), with the same result.

I've now updated to nightly release and seems to work ok :)

@brian6932
Copy link

@adirh3 I have this same issue with a mounted sshfs network drive, on 0.9.91.9995

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working High Priority High Priority BUGS
Projects
None yet
Development

No branches or pull requests

6 participants