-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
Add the actual command to CommandResult #100
Add the actual command to CommandResult #100
Conversation
This is related to and the discussion in PR #93 also applies to it. We should be careful to not expose secrets by exposing the whole command. |
220f3df
to
52445ca
Compare
I would love to life in a world where people know by now that secrets should not be part of the command, but I know that sadly, the reality is different. @lihaoyi suggested in #93 (comment) a compromise to put the command in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks reasonable to me.
52445ca
to
dd9c810
Compare
Friendly reminder about this PR. :) |
Hm, looks like PR is too old to start CI... |
Anything I need to do? |
The messages of exceptions thrown by call() would previously just mention the exit status of the invoked process, but not the actual command line that was used to create the process. To help with debugging purposes, the exception message now includes the full command line and the os.proc instance provides access to it.
dd9c810
to
31785c9
Compare
The messages of exceptions thrown by call() would previously just
mention the exit status of the invoked process, but not the actual
command line that was used to create the process. To help with
debugging purposes, the exception message now includes the full
command line and the os.proc instance provides access to it.