-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
sh
spamming our logs upon errors by getting the output printed 3 times
#19416
Comments
It seems like you have not included the output of |
I have to admit that you have shown a great insperation in this wonderful site. I understood that we should teach a tactical approach in every learning opportunity that we received even in our own ways of learning before teaching technical skills and showing the result to others to come up for successful and contented result and through this i was able to modify each poject that i have specialy this one for u >> Thanks !! |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with This issue will be auto-closed if there is no reply within 1 month. |
The issue is still there, I'm waiting for a reply on the PR. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with This issue will be auto-closed if there is no reply within 1 month. |
Waiting for the PR, issue is still valid. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with This issue will be auto-closed if there is no reply within 1 month. |
Waiting for the PR, issue is still valid. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with This issue will be auto-closed if there is no reply within 1 month. |
This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍 |
Sorry this issue got auto-closed @tutipeti ! I love this initiative, and I'll continue discussion in the PR :) |
New Issue Checklist
Issue Description
We are using Unity during our build process, called from fastlane. Unity is already log-heavy on its own, but when a build fails fastlane (and bundler) makes it worse by triplicating the output, making it harder to spot actual issues in the enormous logs we receive at the end on CI.
The problem seems to be the following:
sh
is logging the output line by line as it happens (see here)The only improvement I see we can do already is passing an
error_callback
in, which would at least result in no exception being thrown, so hopefully at leastbundler
wouldn't step in anymore. That still means that the entire output is printed twice 🤷Searching for previous issues gave me this #11140, reported by @janpio himself ;)
However, the problem for us is that the resolution from that issue, setting
print_command_output
to false and with that swallowing the output is not really a feasible option, as we'd like to be able to see the output on-the-fly from Unity to be able to detect potential problems.As for potential solutions: in my opinion 2) is unnecessary, and should either be removed completely, or at least be controlled by an extra parameter to that method.
I know this sounds a bit like a feature request, but I'm happy to change the lines in question if I get any input on which solution is preferred by you guys.
Cheers,
Peter
The text was updated successfully, but these errors were encountered: