fix: too many open files error in recursive directory traversal #1419
+64
−30
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
previously, recursive directory traversal led to OS errors due to too many simultaneously open file handles. This PR fixes that by making sure we don't read dir until we actually need to.
borngraced
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously, recursive directory traversal caused excessive open file descriptors, leading to OS errors like:
eza --almost-all --recurse >/dev/nullWhich was caused by directories being read too early, keeping file handles open for too long. Now,
to_dironly sets up theDirinstance without reading contents and waits to read directories until needed, reducing open filesfixes: #1387