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
On a Windows machine, when a selected Save Data destination path and the workflow save directory are not on the same filesystem (e.g. one or both are mapped network drives), os.path.relpath on this line erros out with
ValueError: path is on mount '<drive letter>', start on mount '<drive letter>'
How can we reproduce the problem?
Create a new Workflow. Save it to a location on a certain drive. Add e.g. a Multifile widget and a Save Data widget. Set the path on the Save Data widget to a location on a different drive
(On the stated version the file picker comes back up after the exception, so it's not obvious there was an exception - on a colleague's newer version an exception box comes up.)
What's your environment?
Operating system: Windows 10
Orange version: Quasar 1.10.1
How you installed Orange: Windows installer package
Sorry for the trouble - there's a very simple workaround, of course; just save to the same file system. I figured this'd probably be worth submitting anyway.
Thanks for this great software!
The text was updated successfully, but these errors were encountered:
markotoplak
added
bug
A bug confirmed by the core team
and removed
bug report
Bug is reported by user, not yet confirmed by the core team
labels
Feb 5, 2025
What's wrong?
Hi!
On a Windows machine, when a selected Save Data destination path and the workflow save directory are not on the same filesystem (e.g. one or both are mapped network drives), os.path.relpath on this line erros out with
How can we reproduce the problem?
Create a new Workflow. Save it to a location on a certain drive. Add e.g. a Multifile widget and a Save Data widget. Set the path on the Save Data widget to a location on a different drive
(On the stated version the file picker comes back up after the exception, so it's not obvious there was an exception - on a colleague's newer version an exception box comes up.)
What's your environment?
Sorry for the trouble - there's a very simple workaround, of course; just save to the same file system. I figured this'd probably be worth submitting anyway.
Thanks for this great software!
The text was updated successfully, but these errors were encountered: