Uh oh!
There was an error while loading. Please reload this page.
43246: Lineage query NPE while processing an UploadedFile - #20
Merged
Conversation
- handle nodes without an row id in the case of orphaned exp.objects
labkey-nicka
approved these changes
Jun 8, 2021
prep changelog
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale
Avoid NPE in LineageNode constructor for exp.objects that don't have an ID. For example, when the provenance module is enabled, the assay result output rows don't have an ID property, but do have an LSID.
Add support for multiple LSID seeds in a single request and support additional node properties in the response.
Related Pull Requests
Changes