Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
[kubernetes] Log errors to stderr #419
Related to #397.
As you can see in the output above, there is NO information about why
You need to run the same command with debug mode enabled (
Now you can see the error that caused
As you can see, running
Now you are able to see the error that caused
I am really new to bundlewrap and I don't know if this is the best way to solve this problem, especially because it might be a breaking change due to writing to STDERR...
Maybe we could add something like
What do you think?