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
There are scenarios with network drives that then result in blocking the application startup seemingly indefinitely (continuing after 10-12mintures). When the network drives that cause the issue are inspected with a windows file explorer it's also "looking" for a very long time without any progress.
I'm not sure if the root path "" should be considered valid. From my analysis, I would see two tasks:
It should be possible to deactivate this feature or even require it to be activated explicitly
The default behavior should no longer enumerate all drives + files on startup
The text was updated successfully, but these errors were encountered:
As quick fix it might be feasible to either make "rootEntries" lazy or query the "rootEntries" every time in GetEntries. In my application, this will then never get called, while it should not change the current behavior.
It sounds reasonable to require that the inclusion of a FileBrowser needs to be specified on the user/app side. Our "14 - OpenFile" example seems to be a suitable playground for this.
MutableApp.toWebPart
is the default entry used in most demos and applications. This also builds arenderer : Server
withfileSystemRoot = Some "\"
(https://github.com/aardvark-platform/aardvark.media/blob/master/src/Aardvark.UI/MutableApp.fs#L128).On Windows this then performs a
GetAllDrives
and then tries to enumerate all files, but only to check if it is empty: https://github.com/aardvark-platform/aardvark.media/blob/master/src/Aardvark.Service/aardfs/FileSystem.fs#L189There are scenarios with network drives that then result in blocking the application startup seemingly indefinitely (continuing after 10-12mintures). When the network drives that cause the issue are inspected with a windows file explorer it's also "looking" for a very long time without any progress.
I'm not sure if the root path "" should be considered valid. From my analysis, I would see two tasks:
The text was updated successfully, but these errors were encountered: