-
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
[Bug] Workflow fails when artifact file exists, but is empty #1642
Comments
@jessesuen We'd really like this to be fixed in the ongoing release. I'll try to find a fix. |
Ark-kun
added a commit
to Ark-kun/argo
that referenced
this issue
Oct 8, 2019
Empty output artifacts are a valid and desired use case. (Think of `grep` or any other filtering program where one of the outputs can be empty.) Argo failing on empty outputs was a pretty bad surprise for us. Fixes argoproj#1642 The problem was introduced in https://github.com/argoproj/argo/pulls/1247
Here is the PR: #1653 |
Hi, I am new to Argo and Kubernetes. Which version did this issue get resolved? I'm using argo v2.4.3, but still getting this error:
|
2.5.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a BUG REPORT or FEATURE REQUEST?:
BUG REPORT
What happened:
Workflow fails when output artifact file exists, but is empty.
It's a blocking issue for us since we have tasks where some outputs are often empty or some mutually exclusive outputs.
What you expected to happen:
Empty output files should be a valid scenario.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
Other debugging information (if applicable):
The text was updated successfully, but these errors were encountered: