Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File save causes exception if the workflow and destination are not on the same filesystem #7018

Closed
0xDBFB7 opened this issue Feb 5, 2025 · 1 comment · Fixed by #7019
Closed
Labels
bug A bug confirmed by the core team

Comments

@0xDBFB7
Copy link

0xDBFB7 commented 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

ValueError: path is on mount '<drive letter>', start on mount '<drive letter>'

How can we reproduce the problem?

Image

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!

@0xDBFB7 0xDBFB7 added the bug report Bug is reported by user, not yet confirmed by the core team label Feb 5, 2025
@0xDBFB7
Copy link
Author

0xDBFB7 commented Feb 5, 2025

Whoops - dupe of #6685

@0xDBFB7 0xDBFB7 closed this as completed Feb 5, 2025
@markotoplak 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
@markotoplak markotoplak reopened this Feb 5, 2025
@markotoplak markotoplak marked this as a duplicate of #6685 Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A bug confirmed by the core team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants