You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a copy of heroku/legacy-cli#1214 (2014) on old project. The behavior still exists, and is still a problem for me for exactly reasons original reporter explained well, I'll just copy it:
Right now, all output from a heroku run session seems to be returned on stdout.
I'm running a script via heroku run as part of a workflow, and I've hit a snag since the script I'm running outputs to stderr too, and I want to ignore that output.
This is a copy of heroku/legacy-cli#1214 (2014) on old project. The behavior still exists, and is still a problem for me for exactly reasons original reporter explained well, I'll just copy it:
Right now, all output from a heroku run session seems to be returned on stdout.
I'm running a script via heroku run as part of a workflow, and I've hit a snag since the script I'm running outputs to stderr too, and I want to ignore that output.
Simple test case (e.g. script.sh):
Works locally:
$ ./script.sh This is error output. $ ./script.sh 2> /dev/null (no output)
Doesn't work via heroku run:
The text was updated successfully, but these errors were encountered: