Leo

Okay, at least the timezone can be found in the zoneinfo.zip file. Haven't mentioned it, but I also tried "Europe/Paris" and this had exactly the same behaviour of not starting...

So, am I the only one who has this buggy behavior or is simply no one using time zones in Argo Workflows?

@Hunter-Thompson I'm on `3.3.8` not `3.2.8`, typo or are you really on `3.2.8`? Maybe a downgrade could help then.

hmm interesting, how did you deploy your instance? I deployed via bitnamis helm chart, maybe the chart has an issue deploying a "broken" state. Don't know how it could cause...

Hunter-Thompson thanks for that. @alexec I guess that should be a `... | grep version` there. So I got: `time="2022-07-14T16:00:04.561Z" level=info msg="Starting Workflow Controller" defaultRequeueTime=10s version=v3.3.7` Do the server and...

definitely need this, too. I even thought that this is actually the default behaviour for jobs in the same queue to be executed sequentially.

Stumbpled over this issues here, got the same problem on centos 7, java version 1.8.0_77, javac version 1.8.0_77. Installed ant, installed maven. Ran "ant dist.lin64" and get: `Buildfile: /srv/jitsi_components/jicofo/build.xml BUILD...

I've downloaded the maven-ant-task-2.1.3.jar manually and as you can see I'm using the "-lib" param. I've checked the build.xml, ran the command: $ mvn dependency:get -DartifactId=maven-ant-tasks -DgroupId=org.apache.maven -Dversion=2.1.3 the result:...

running on centos 7. $ mvn -version Apache Maven 3.0.5 (Red Hat 3.0.5-16) Maven home: /usr/share/maven Java version: 1.8.0_77, vendor: Oracle Corporation Java home: /usr/java/jdk1.8.0_77/jre Default locale: en_US, platform encoding:...

okay, got the current maven version. `Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00) Maven home: /opt/apache-maven-3.3.9 Java version: 1.8.0_77, vendor: Oracle Corporation Java home: /usr/java/jdk1.8.0_77/jre Default locale: en_US, platform encoding: UTF-8 OS...