We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
During #8367 we noticed that this check may be obsolete due to the agglomerates now always being looked up by segment id in the current mapping.
Maybe we can remove it? Should be double-checked.
Also, with the same justification, should we also duplicate the agglomerateGraph2.segments.contains(segmentId2) assertions for agglomerateGraph1?
agglomerateGraph2.segments.contains(segmentId2)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
During #8367 we noticed that this check may be obsolete due to the agglomerates now always being looked up by segment id in the current mapping.
Maybe we can remove it? Should be double-checked.
Also, with the same justification, should we also duplicate the
agglomerateGraph2.segments.contains(segmentId2)
assertions for agglomerateGraph1?The text was updated successfully, but these errors were encountered: