Standard Output of "brew tap" is Empty When Run as a Sub-Process from a Separate Program #4197
Unanswered
buresdv
asked this question in
Everyday usage
Replies: 1 comment 4 replies
-
Try capturing standard error as well. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Output of
brew config
Output of
brew doctor
Description of issue
Hey everyone,
I don't know if this is a programming error on my part or something to do with Brew itself, but I have exhausted all other options, so I'm asking here.
I'm developing a helper GUI program for Brew for macOS. This program executes brew commands through sub-processes and then captures their outputs.
This works great with most commands like brew install and brew update. The process finishes and returns the output of the command as it should.
However, I have run into a problem with the commands brew tap and brew untap. For some reason, these two commands return absolutely nothing. When I execute them, I can see the command's real-time output in the terminal, but when I try to capture the final result through standard output, it's completely empty. To see what I mean, check out this video.
As you can see, the command runs and outputs its usual output into the console. At the end, I select the line which starts with "Result", which should contain the full output of the command as it does with other commands, but as you can see, it's completely empty.
If you want to inspect the relevant code of my program, the function for executing and capturing command outputs is here and an example of running a command and capturing its output is here.
I have scoured Stack Overflow, Apple development forums and asked in various programming communities, but nobody knows why this is happening.
Beta Was this translation helpful? Give feedback.
All reactions