Fix a bug which cause scripts on command line run out of order#171
Open
alexzhuustc wants to merge 1 commit into
Open
Fix a bug which cause scripts on command line run out of order#171alexzhuustc wants to merge 1 commit into
alexzhuustc wants to merge 1 commit into
Conversation
…cripts out of order.
e.g.
nodeunit a.js b.js c.js d.js
the output may looks like
-> b.js
-> c.js
-> a.js
-> d.js
I believe it's not an intended design. Because all other codes are carefully handle path in series mode.
Contributor
|
+1 on this. |
|
Are there plans to integrate this soon? |
|
4 years later, why is this PR unmerged ? It fix an error that occur very often and that can be very annoying, depending on your use case. |
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
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.
There is a code processes path in parallel mode which MAY cause run scripts out of order.
e.g.
nodeunit a.js b.js c.js d.js
the execute order may looks like
-> b.js
-> c.js
-> a.js
-> d.js
I believe it's not an intended design, as all other codes are carefully handle path in series mode.