-
Notifications
You must be signed in to change notification settings - Fork 72
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
Why can't I run exec.Command("app do something") call inside custom predictor? #145
Comments
It seems that you forgot datacmd.Run()? |
Hi, thank you for reply. cmd.Output() method under the hood runs Run() and Wait(). But this issue I mentioned is not solved. I suppose it's somehow can't run subprocess on my Mac or whatever because it's not even making request (although no error output either). |
Oh, right, sorry I missed it.
This is usually the better approach in any case 👍 I see that you don't check the error returned from the |
In any case, I tried to reproduce it on my linux machine and didn't found an issue: The program:
In the terminal:
Then I Can you please check on your machine if you get the same behavior? |
I would like to predict not hardcoded options but pull them from daemon every time.
For example I input command
app user remove
, click TAB, and cli would offer me list of users which pulled by calling exec.Command("cli-get-users')Output is always empty, but when I run this code inside unit test, output is present and we're all good.
If this is expected behaviour please someone explain or point me to explanation why it's not working.
The text was updated successfully, but these errors were encountered: