-
Notifications
You must be signed in to change notification settings - Fork 36
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
signac view
fails when statepoints contain forwardslashes
#213
Comments
I think the proper behavior here is to just throw a more descriptive error message. Right now it just gives a permission denied error in this case, we should at least change it to raise an Exception that informs the user why it doesn't work. I don't think that this is necessarily something that we should support, because it would require modifying the values to avoid containing file separators. |
I agree that adding a more descriptive error message and potentially suggesting a work-around is the way to go. We have been pretty liberal about what a state point key and value may contain as long as it is JSON-encodable and issues like that are kind of bound to happen. My suggested solution is to explicitly check for @klywang Would that be a satisfactory solution? |
@csadorf Yeah that sounds good! |
Just to clarify the behavior we want: |
Yes, I think that's the best option. We could potentially disallow them in 2.0, but I don't think it's necessary since it only causes problems for views. |
Resolved by #233. |
Description
signac view
cannot create folders when statepoints contain forward slashes (ie, if a statepoint value is '/oasis/scratch/some_file.txt')To reproduce
signac view
Example of statepoint:
{'pot_file': '/oasis/scratch/path/to/file/some_file.out'}
Error output
Error: [Errno 13] Permission denied: '/oasis'### System configuration
Please complete the following information:
The text was updated successfully, but these errors were encountered: