Skip to content
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

Document possible limitations with CmdRunner module #95

Open
senorprogrammer opened this issue Jun 2, 2020 · 1 comment
Open

Document possible limitations with CmdRunner module #95

senorprogrammer opened this issue Jun 2, 2020 · 1 comment

Comments

@senorprogrammer
Copy link
Contributor

Per the examples raised in this issue, CmdRunner cannot run everything. Some documentation and tips for trouble-shooting would be helpful.

@tnwei
Copy link
Contributor

tnwei commented Aug 23, 2021

Arrived here from the aforementioned issue. I think referring to the fact that CmdRunner relies on Golang's exec.Command() is a good piece of info for troubleshooting. It does not support shell expansion, which I believe would be a common gotcha.

Off-topic, but wonder if it is possible to pipe the command output directly to stdout so that more info is available for debugging other than the exit statuses provided by Golang.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants