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

Analysis network breaks when no-with-in-connection artifacts are selected. #3224

Closed
antgonza opened this issue Nov 30, 2022 · 0 comments
Closed

Comments

@antgonza
Copy link
Member

If an analysis has multiple root artifacts and the users creates a job that uses an artifact that doesn't belong with in the network the GUI breaks.

Example:
a -> (input a) b -> (input b) c
d -> (input d) e -> (input a and e) [brakes!]

Example job: dc69f829-7a35-4610-b5c9-3f018385c9a8

Error:

KeyError                                  Traceback (most recent call last)
Input In [41], in <cell line: 4>()
     28 if jstatus != 'success':
     29     # Connect the job with his input artifacts, the
     30     # input artifacts may or may not exist yet, so we
     31     # need to check both the input_artifacts and the
     32     # pending properties
     33     for in_art in n_obj.input_artifacts:
---> 34         _add_edge(edges, nodes[in_art.id],
     35                   nodes[n_obj.id])
     37     pending = n_obj.pending
     38     for pred_id in pending:

KeyError: 159616

A couple of possible solutions are (1) to not allow users to select between network artifacts, or (2) allow the GUI to inspect within analysis networks.

antgonza added a commit to antgonza/qiita that referenced this issue Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant