fix(compile): panic when compiled with --no-terminal flag #28823
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.
This works towards fixing #27730 and #21091.
When compiled with the
--no-terminal
flag under windows there are some issues related to stdin, stdout and stderr.This pull request fixes the panic when during bootstrap the terminal type is requested.
Previously it would return the error if the terminal was not valid, instead it now returns UNKNOWN.
The dummy stdin that is than provided instantly pushes null for some reason.
However this tries to do a
debugLog
which is not possible yet, as we are still initiating.I don't see the use for this push, so I removed the line.
If it is needed for something please let me know.
This PR does not fully fix the issue yet, as there is a similar problem in deno_core's
isTerminal
op, see this pull request.