-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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.
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
Panic occurs when running `deno test | hoge #15767
Comments
It shouldn't panic, but obviously it isn't going to work. |
This doesn't affect deno test only but all deno commands, "fixing" this would require changing all The only improvement I can see is not printing that message on this kind of situation, but I'm not sure how would one detect this. |
The messages stability are not guaranteed by rust API as far as I know, but it should still mostly work, and if it doesn't it just shows the current behavior |
@sigmaSd could you open a PR that implements this solution? |
Currently if we get an error from rust stdio, like `Broken pipe` we print our usual header and advise the user to report this as a bug. But this is not a bug in deno, so this pr add a heuristic to detect this and if its the case (error coming from stdio), just do the normal panic without our deno header. Relevant issues: denoland#15767 denoland#14746 denoland#15045 denoland#15982
Summary
Panic occurs when running
deno test | hoge
It seems that panic occurs when using a non-existent command with pipe.
The text was updated successfully, but these errors were encountered: