-
Notifications
You must be signed in to change notification settings - Fork 42
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
The copy_files
keyword can fail when using the output directory from a prior @job
with Parsl
#1776
Labels
Comments
copy_files
keyword argument fails when using the output directory from a prior @job
and using Parsl or Covalentcopy_files
keyword argument fails when using the output directory from a prior @job
with Parsl or Covalent
copy_files
keyword argument fails when using the output directory from a prior @job
with Parsl or Covalentcopy_files
keyword can fail when using the output directory from a prior @job
with Parsl or Covalent
copy_files
keyword can fail when using the output directory from a prior @job
with Parsl or Covalentcopy_files
keyword can fail when using the output directory from a prior @job
with Parsl
This was referenced Mar 25, 2024
3 tasks
Andrew-S-Rosen
added a commit
that referenced
this issue
May 30, 2024
## Summary of Changes Closes #1776. Requires: - Parsl/parsl#3111 --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Details about the quacc environment
What is the issue?
When using the
copy_files
keyword argument and passing in something like{directory: "*"}
wheredirectory
is anAppFuture
from a prior run, Parsl won't know to autoresolve the dictionary, and a crash will occur.Minimal examples:
AppFuture
s do not get implicitly resolved Parsl/parsl#3108This will be solved upstream in Parsl via the following PR:
How can we easily reproduce the issue?
Pytest examples:
Parsl:
The text was updated successfully, but these errors were encountered: