generated from AgnostiqHQ/covalent-executor-template
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Support more robust path handling with remote_workdir
#91
Comments
Andrew-S-Rosen
changed the title
Support more robust path handling
Support more robust path handling with Mar 6, 2024
remote_workdir
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
What is happening?
Related to #95, when one specifies the
remote_workdir
with a path like~/my/dir
, it raises an error upon trying to parse the pkl file. The UI shows [Errno 1] : PosixPath('~/test/ef5861af-7b92-4dbc-a52c-eb83bb137496/node_0/result-ef5861af-7b92-4dbc-a52c-eb83bb137496-0.pkl').How can we reproduce the issue?
What should happen?
Filepaths like
~/my/dir
should workAny suggestions?
Wrap the file path in
Path().expanduser().resolve()
client-side before the electron is launched. As a stretch goal, I would even suggest trying to support something like$SCRATCH/my/dir
by wrapping the path call withos.path.expandvars()
on the client side too.You can basically copy what I have done in the
covalent-hpc-plugin
in terms of file path handling, such as here.The text was updated successfully, but these errors were encountered: