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
It seems like any output to stderr, including output that may be entirely normal, such as lines like
Warning: Permanently added the ECDSA host key for IP address '140.82.113.3' to the list of known hosts.
will cause this action to fail the actions build. The build should only be failed when the actual git operation fails.
Reproduction Steps
Unsure what exact conditions can trigger this issue -- but anything causing git to produce output on stderr without a push failure would trigger this issue
Thanks for reporting this. There's another similar issue reported here.
I've been trying to think what the best way to solve this is, as the rejection occurring here is potentially catching failures. @PartyLich handled it here in a fork, but this isn't a very scalable solution.
I'm wondering if we shouldn't throw an error in this case, but instead warn of a potential problem or filter for common scary words such as fatal: before throwing. From what I understand all fatal errors look something like fatal: Something went wrong... so it may be possible to just check if (!rejected && pushResult.stderr.includes('fatal:')) throw new Error(pushResult.stderr) or if (!rejected && pushResult.stderr.startsWith('fatal:')) throw new Error(pushResult.stderr)
Describe the bug
It seems like any output to stderr, including output that may be entirely normal, such as lines like
will cause this action to fail the actions build. The build should only be failed when the actual git operation fails.
Reproduction Steps
Unsure what exact conditions can trigger this issue -- but anything causing git to produce output on stderr without a push failure would trigger this issue
Logs
See
https://github.com/SpongePowered/math/runs/7374387288?check_suite_focus=true#step:11:59
Workflow
The relevant use of this action is:
from a workflow shared across the organization
Additional Comments
n/a
The text was updated successfully, but these errors were encountered: