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
Currently when you export to PDF or HTML, the location of the exported file is the root of the user's machine (e.g. /filename.pdf)
Users working on remote hosts (e.g. Azure ML compute, Azure VM) are sometimes unable to write to the root of their host. They have to manually change the export path to a directory that they can write to.
Ideally the exported path defaults to either the root of the user's workspace, current working directory, or the directory in which their Notebook is in.
The text was updated successfully, but these errors were encountered:
Bug - as this breaks simple HTML in AML (the export doesn't work with default directory & it needs to be changed to workspace) - could be permissions or the like.
Either way, not the best default experience even though there's a work around (not obvious either)
Currently when you export to PDF or HTML, the location of the exported file is the root of the user's machine (e.g. /filename.pdf)
Users working on remote hosts (e.g. Azure ML compute, Azure VM) are sometimes unable to write to the root of their host. They have to manually change the export path to a directory that they can write to.
Ideally the exported path defaults to either the root of the user's workspace, current working directory, or the directory in which their Notebook is in.
The text was updated successfully, but these errors were encountered: