This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[orchestra] extract graph logic and enhance with cycle detection + coloring #5614
Merged
paritytech-processbot
merged 18 commits into
master
from
bernhard-orchestra-extract-graph-logic
Jun 6, 2022
Merged
[orchestra] extract graph logic and enhance with cycle detection + coloring #5614
paritytech-processbot
merged 18 commits into
master
from
bernhard-orchestra-extract-graph-logic
Jun 6, 2022
Conversation
This file contains 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
Coloring/annotating cycles properly is pending, the logic is already there:
|
Currently kosaraju_scc returns invalid cycles, which is yet to be investigated.
A strongly connected cluster contains at least one cycl, but could include more. So this should be distringuished in the implementation to avoid some confusion.
with the output of:
(pre splitting the network bridge #5616 ) |
ordian
approved these changes
Jun 3, 2022
drahnr
commented
Jun 3, 2022
sandreim
approved these changes
Jun 6, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. It would also be really helpful to have the option to create a graph only with only the cycle.
I'll create a separate PR that will add these graphs of cycles only |
bot merge |
al3mart
pushed a commit
that referenced
this pull request
Jul 14, 2022
…loring (#5614) * extract graph * move into scope * remove dead code * add special nodes * avoid some clones * better doc * maybe better to use ✨ * print all cycles, or an error Currently kosaraju_scc returns invalid cycles, which is yet to be investigated. * don't print tiny cycles, if there is nothing to unvisited anymore, there is a cycle * make print better * fmt ffs * correct: cycle -> scc A strongly connected cluster contains at least one cycl, but could include more. So this should be distringuished in the implementation to avoid some confusion. * fix loop exit condition * add a test for kosaraju behavior * unify on 'component' * disable graph by default https://github.com/paritytech/ci_cd/issues/433 * chore: fmt * move graph only to graph_helpers
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
A0-please_review
Pull request needs code review.
B0-silent
Changes should not be mentioned in any release notes
C1-low
PR touches the given topic and has a low impact on builders.
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.
NetworkBridge
will always cause a cycle now)