fix: When both InputStream and ErrorStream exist, copyStream cannot guarantee sequential execution #735
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.
When both the input stream and the error stream exist in the script processor, the "copyStream" cannot guarantee sequential execution of these streams.
What is the purpose of the change
To guarantee that the output of the task in the script processor is ordered.
Brief changelog
To move the log submits to when the task completed.
Verifying this change
For example, a python script as the following:
Both the input stream and the error stream exist in this python script, we found that the execution result outputs of this python script were unordered when we view its logs. Therefore, we remove the omsLogger submits in the "copyStream" and move it to when the task completed.