-
Notifications
You must be signed in to change notification settings - Fork 1k
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
AttributeError: 'NoneType' object has no attribute 'element_identifier' #18012
Comments
Can you check what elements you have in history_dataset_collection_association 2521822 ? |
I am not sure what exactly I should look for, maybe can you give us an SQL query to run?
|
Thanks, that's all I need. I think |
Alright, I think the only way users can submit a collection like this is if they drag it from the history panel into the input field, which bypasses a lot of validation (a hack we should probably disallow by also validating dragged input ?). I see that the dataset collection matcher correctly filters out collections that are not populated, so #18023 is just going to raise an appropriate exception if a user tries to submit such a collection as input. Again though, you probably want to figure out what happened to that collection. |
Should be fixed with #18023 ... we just can't work with collections in this state if we don't persist the request, which we're going to do in #17393, so that this will behave a little more like in workflows, where this works because we simply try again at the next scheduling iteration. That's of course also not going to be the silver bullet, since the output of that job won't be created until the request can be processed, but I don't really see a way around this. It should be a fairly rare situation fortunately. |
Thanks a lot @mvdbeek ! |
Found this in our logs, on 24.0.
The text was updated successfully, but these errors were encountered: