fix: Speed up repo discovery with parallel traversal - #10
Merged
Conversation
Walk sibling directories concurrently instead of draining each child sequentially, and match excludeDirs against the child path so exclusions actually prune subtrees.
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
1 participant
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.
Summary
list_fzfregressed to a serial depth-first walk: each child directory's channel was fully drained before the next sibling started. Now siblings are traversed concurrently and merged into one channel, so results stream from all branches in parallel.excludeDirswas checked against the parent (basedir) instead of the child path, so it never pruned anything. Now matched against the child, so exclusions actually take effect.