Skip to content
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.

Sign up for GitHub

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

Jump to bottom

fix: Avoid blowing the call stack when processing many files #133

Merged
merged 5 commits into from
Apr 8, 2024
Merged

fix: Avoid blowing the call stack when processing many files #133

merged 5 commits into from
Apr 8, 2024

Conversation

phated
Copy link
Member

@phated phated commented Apr 8, 2024

I've removed now-and-later to instead push a resolve action into the queue that processes symlinks.

Fixes #125

@phated phated requested a review from yocontra April 8, 2024 01:32
@phated phated merged commit bb21c9d into master Apr 8, 2024
14 checks passed
@phated phated deleted the phated/max-call-stack branch April 8, 2024 04:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@yocontra yocontra Awaiting requested review from yocontra

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Updating from v8.0.0 to v8.0.1 causes RangeError: Maximum call stack size exceeded
1 participant
@phated