-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Command being replaced into the workflow: Golang fundamental flaw bug - again #5192
Comments
Can you confirm if this is a regression and if so which version it is regresses from. |
@alexec - Just double checked and I found the same behaviour on the version |
And did it work in v2.12.9? |
Yep @alexec, same error on version 2.12.9 😢 |
Can you try v2.11.8? |
Hey @alexec, |
By "couldn't replicate" do you mean it is not a problem is v2.11.8? Or something else? |
|
Can I ask you to test v2.12.8? I think the revert in that version maybe re-introduced a bug. |
Signed-off-by: Alex Collins <[email protected]>
Signed-off-by: Alex Collins <[email protected]>
Signed-off-by: Alex Collins <[email protected]>
Summary
I’m facing a quite weird issue when I’m trying to suppress the stderr from the phpunit tests executions and not sure if the workflow command translation is replacing and send the command to the container.
Issue
We’re appending
2> /dev/null
at the end of the phpunit binary (e.g:$phpunit 2>dev/null
) - this is a workaround to avoid the stderr payloads being printed during the test execution.Noticed the command at the Summary tab (name value) has changed from
2> /dev/nul
l to2u003e/dev/null
The images are showing the modified command along with the container log output:
Console output
ArgoWF Summary output
Diagnostics
The phpunit is failing due the incorrect command parameter received from the workflow (
command
).Expected:
phpunit --group unit 2> /dev/null
Found:
phpunit --group unit 2\u300e/dev/null
Kubernetes provider: 1.18.15-gke.1100
Argo Workflow version: V3.0.0-rc3
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: