botbotbot

Results 8 comments of botbotbot

I got the same problem. I try to rollback Mongo database from version 3.4 to 3.2 and the error is gone.

I'll take Color Helpers, Text Helper in Utilities

I can't reproduce this one on v3.4.1 and latest on master branch. I tested with https://github.com/argoproj/argo-workflows/blob/master/examples/continue-on-fail.yaml Could you help to provide example workflow that able to reproduces the issue ?

I faced this issue too. I would like to help to clean it up. Do you have any suggest approach ?

> There are already environment variables that controls this test I see then how about just update document and git hook pre-commit message. Let me know if you have another...

Could you help to merge ? I rebased and pushed to re-trigger e2e that failed and the auto-merge is gone.