You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: