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
The s3 prefix is used when creating the custom encompassing drive for the DriveBrowser. The s3 path gets displayed at the top of the Launcher tab, as it is connected to the DriveBrowser. The behaviour is the same when using the default FileBrowser, without the prefix s3 (this can be observed by opening a new Launcher from the default FileBrowser).
This is also related to the temporary solution we merged for having the Launcher work with the DriveBrowser, #61. It uses the IFileBrowserFactory to track the current file browser used and defaults to the DriveBrowser when first launching JupyterLab as it get the recently added file browser, if none was in focus. Once we have the Launcher functionalities fixed upstream, the path will still be displayed, but it will either be the local one from the default FileBrowser or the s3 one from the DriveBrowser.
Here is the issue where we are discussing the Launcher behaviour: #45
Tested in SageMaker JupyterLab, as well as local installation of JupyterLab
When I start navigating a bucket, the navigation path gets printed in Launcher tab. Even when I dont navigate the string
S3:
gets printed.Expected
Launcher tab to not see the S3 path
The text was updated successfully, but these errors were encountered: