Perhaps this is more a feature request than a bug. Anyhow, curious to hear your thoughts!
Summary
Argo Workflows show workflows that are waiting on a semaphore lock as having status "Running", whereas they are technically pending. Not only does this thus falsely report the status of the workflows, it also makes it harder to measure the efficiency of workflows as a potential delay due to locking would be incorporated.
Note, I am working with a Argo Events Github Sensor triggering workflows. Perhaps this issue is more specific to Argo Events and I should open this issue there?
What happened/what you expected to happen?
For the workflow to remain in pending.
What version of Argo Workflows are you running?
3.2.6
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
Perhaps this is more a feature request than a bug. Anyhow, curious to hear your thoughts!
Summary
Argo Workflows show workflows that are waiting on a semaphore lock as having status "Running", whereas they are technically pending. Not only does this thus falsely report the status of the workflows, it also makes it harder to measure the efficiency of workflows as a potential delay due to locking would be incorporated.
Note, I am working with a Argo Events Github Sensor triggering workflows. Perhaps this issue is more specific to Argo Events and I should open this issue there?
What happened/what you expected to happen? For the workflow to remain in pending.
What version of Argo Workflows are you running? 3.2.6
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.