Isitha Subasinghe

@terrytangyuan I've had issues with the Github tests too, we should try and address this somehow, additionally the maintainers should take note that failed Github checks don't necessarily mean the...

It seems to be `FunctionalSuite/TestOutputArtifactS3BucketCreationEnabled` that is causing issues.

This is no longer the behaviour described above. @SatabrataPaul-GitAc check commit 6b086368f6480a2de5e2d43eec73514de0ad01ac 

Note that I am viewing this information on the UI's 'message' field I was not able to replicate this issue. I get "workflow shutdown with strategy: Stop". This corresponds to...

I had a look at this and I think this behaviour is fixable if "The same issue does not occur if the mutex is on the container template or at...

Okay this was quite difficult to debug but I think I finally found the reason as to why this doesn't work. Let's imagine we have a workflow name called "xyz"...

In workflow/sync/sync_manager.go the behaviour of how mutexes are implemented looks wrong to me. I believe this is what is causing #8684. This is the issue: On restart, the key to...

Thanks for that @Gibstick I will check why this works as well

@caelan-io I can confirm this issue is still a problem unfortunately. I believe ~~my original comment is still correct~~ something else is going on. The comment I made previously is...

https://github.com/isubasinghe/argo-workflows/tree/fix-deadlock-sync-manager Please check before.txt and after.txt to see the logs after the deadlock. before.txt and after.txt are the relevant files. After the controller restart, the mutex is acquired by argo/deadlock-test-sn8p5...