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

do not auto-add save_result when export_workspace is used #623

Closed
jdries opened this issue Sep 20, 2024 · 3 comments
Closed

do not auto-add save_result when export_workspace is used #623

jdries opened this issue Sep 20, 2024 · 3 comments
Assignees

Comments

@jdries
Copy link
Collaborator

jdries commented Sep 20, 2024

Current behaviour:

if result_node.process_id == "save_result":

If last node is not save_result, then add it automatically.

Better: check the entire graph for save_result processes? If there are any, then the user probably knows what he's doing.

@soxofaan
Copy link
Member

soxofaan added a commit that referenced this issue Sep 24, 2024
- Check whole process graph for pre-existing `save_result` nodes, not just final node
- Disallow ambiguity of combining explicit `save_result` and download/create_job with format
@soxofaan
Copy link
Member

started working on draft at #630

soxofaan added a commit that referenced this issue Sep 25, 2024
…583, #391)

Make it more consistent with `download`
@soxofaan soxofaan self-assigned this Sep 25, 2024
soxofaan added a commit that referenced this issue Sep 25, 2024
- Check whole process graph for pre-existing `save_result` nodes, not just final node
- Disallow ambiguity of combining explicit `save_result` and download/create_job with format
soxofaan added a commit that referenced this issue Sep 25, 2024
…583, #391)

Make it more consistent with `download`
@soxofaan
Copy link
Member

done with 58f0205

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants