-
Notifications
You must be signed in to change notification settings - Fork 24
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
BUG: append_name for Flows generated as a Response #639
Comments
Hi @JaGeo Not sure if it is a bug but at least it is definitely a use case. Somehow what's missing is the dynamic application of the append procedure, similar to e.g. what is done with update_metadata (in which there is a dynamic argument, by default True). I'll let @utf comment on this but it seems reasonable to add this feature. |
I agree with @davidwaroquiers, we could add a jobflow/src/jobflow/core/job.py Lines 935 to 937 in 11034dd
|
@utf @davidwaroquiers adding a dynamic option would be great and would help with solving my issue. |
I guess it would be good (and more consistent) to also add the same filtering options. Should then this stay within append_name or be a new update_name method? |
I am trying to implement a more complex workflow (see materialsproject/atomate2#903). I need to renae jobs to work on the corresponding tests.
This results in
Is there another way to rename that I am overlooking? I would have hoped that "my_function" also gets renamed.
The text was updated successfully, but these errors were encountered: