Harden SBOLExplorer indexing and SPARQL dataset handling - #160
Merged
Conversation
cjmyers
approved these changes
Jul 31, 2026
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 free
to 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.
This PR makes SBOLExplorer indexing more deterministic and portable across SPARQL stores. Explorer initialization occurs only after the index-update functions are defined, allowing fresh deployments to build their first index reliably. Index maintenance queries operate over the endpoint’s complete dataset without sending an empty default-graph-uri, while search queries extract explicit FROM clauses independently of the SELECT projection for both result and count queries. CI now builds SBOLExplorer directly from the checked-out source and runs focused tests covering startup ordering, query transport, and dataset scoping.