argoproj / argoproj/argo-workflows

Semaphore Locked Workflows are shown as Running

Open
#7,620 3 comments 3 reactions 0 assignees View on GitHub
area/mutex-semaphore
Dominant language
Go
Stars
17k
Forks
3.7k
Avg merge
1d 20h
Merged PRs (30d)
138

Description

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 👍.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the semaphore-lock behavior described for Argo Workflows 3.2.6, then trace how workflow status is assigned while a lock is pending. Done means a workflow waiting on a semaphore is reported as pending rather than running, without counting lock wait time as workflow execution.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.