-
Notifications
You must be signed in to change notification settings - Fork 19
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
Partial Orderings #133
Comments
@mkw for visibility |
This was referenced Oct 28, 2020
In v1beta, I've noticed this far less often. I suspect it's due to the improved data model. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In investigating #131 yesterday, I noticed that part of our client-side code is incomplete. As a result, queries for a
topology
can return partial orderings instead of correct orderings.How does this happen?
The most common way this comes up is when there is a cycle in the graph. Cycles in graphs introduce complications. For one, it's possible that there is no correct ordering.
Current Situation
When the
deps
command-line tool runs, it will output an ordering. We currently do not provide any feedback that the ordering is partial or correct. We don't provide a sense of how many modules are omitted.Improvements
The text was updated successfully, but these errors were encountered: