-
Notifications
You must be signed in to change notification settings - Fork 28.9k
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
Installing malicious extension via cli should not dump a stack #42115
Comments
@sandy081 I actually get a very different output when running from sources:
This indicates that errors are not being propagated back. Here's the culprit: That line just swallows up errors and doesn't let them reach the outside. |
@joaomoreno Above line returns the wrapped errors. Issue is at different place (see the above fix). Some how this only happens when installed from cli otherwise, error is properly propagated (from workbench for eg). Please take a look if you want to show the complete stack trace or not in CLI. IMO it is fine to show it. |
@sandy081 You're absolutely right! Good fix. I think we shouldn't show the stack, but just the exception message. |
@joaomoreno will add the test extension back to the blacklist for testing. |
The text was updated successfully, but these errors were encountered: