-
Notifications
You must be signed in to change notification settings - Fork 2
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
Some errors are emitted to stdout instead of stderr #161
Comments
browsing history I noticed commit 9bb6520 changed |
Good catch. There should be no |
not sure about removing console altogether, at least the error message for multiple roots is useful (see the related PR) |
Not sure if that changed but console.log was or is synchronous so it's better to use an abstraction for logging that can write to console but doesn't do so unless we tell it to. Not sure what's the latest and greates logger though. |
yes, we have the proper logging abstractions in place and all the other telemetry stuff. My guess is that this is a special case because we are at the boundaries of the system, where even the logging abstractions may not be available yet. |
No description provided.
The text was updated successfully, but these errors were encountered: