Increase maximum queue size to 20_000#12218
Closed
tomquist wants to merge 1 commit into
Closed
Conversation
Unfortunately we hit the maximum queue size with our code base even though there’s no infinite cycle.
Collaborator
|
Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/30509/ |
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 1991c3e:
|
Contributor
|
Can you share a reproduction? I doubt that it is an internal Babel bugs. |
Member
|
Closing since you didn't reply to #12218 (comment), so I assume it's ok now! |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
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.
Due to our tests we hit the "Infinite cycle detected" error on seemingly random changes. It seems to be related to the queue size exceeding a hard-coded limit. Not sure if 20000 is a good limit but 10000 already seemed to be kind of arbitrary.