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

NUTFS protocol - Local scan path directory listing empty on switch #307

Closed
hoonyeah opened this issue Jun 16, 2021 · 3 comments
Closed

NUTFS protocol - Local scan path directory listing empty on switch #307

hoonyeah opened this issue Jun 16, 2021 · 3 comments

Comments

@hoonyeah
Copy link

Describe the bug:

Nut 3.1
Tinfoil 12.0
NUTFS via LAN

Issue - Directory listings for specified "local scan paths" are empty on switch.

I do, however, see root drive listings and am able to browse through windows trees to find files and the directory contents does successfully load this way. (I am opening another bug to hopefully lock this down and not show all drives connected to NUT server, but this is unrelated.)

Reproduce
Steps to reproduce the behavior:

Start nut gui 3.1
Wait for GUI to load.
Connect switch.
Launch Tinfoil 12.0
Configure Local Scan Path on NUT GUI
Configure NUTFS path to local LAN pc on switch
Browse to configured NUTFS path on switch

Actual behavior
Initial Directory listing:
SWITCH --< configured local path
B --< Local root drive on nut server
C --< Local root drive on nut server
X --< Local root drive on nut server

Drill into SWITCH, and it's empty.
Confirmed was working on Nut 2.5

Expected behavior
Drill into configured local path and directory contents should load.

@blawar
Copy link
Owner

blawar commented Jun 30, 2021

This should be fixed in master, can you confirm?

@hoonyeah
Copy link
Author

hoonyeah commented Jul 1, 2021

Dumb comment from dumb windows user. Do I have to compile?
Did not work with latest windows executable, but that's dated January.
https://github.com/blawar/nut/releases/tag/v3.1

@blawar
Copy link
Owner

blawar commented Jul 4, 2021

you will have to wait until we do another binary release if you cant run from source @hoonyeah . Will likely be next week.

@ghost ghost closed this as completed Jul 15, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants