Hang Nguyen

I got a different response ``` Original curl https://httpbin.org/response-headers\?access_token\=faketoken\&token_type\=Bearer { "Content-Length": "128", "Content-Type": "application/json", "access_token": "faketoken", "token_type": "Bearer" } go-httpbin curl http://httpbin:9100/response-headers\?access_token\=faketoken\&token_type\=Bearer { "access_token": [ "faketoken" ], "token_type": [ "Bearer"...

@paolocarta Just take some test and check. I think this may have duplicate trigger from Gitlab side. I also see some issue report about Gitlab Webhook Duplication on Gitlab

@bygui86 These are some link https://github.com/n8n-io/n8n/issues/2042 https://gitlab.com/gitlab-org/gitlab-foss/-/issues/15 Today I've tested with latest version of Argo Workflow and Argo Event. I've used Gitlab Event source from examples - with replicas 2:...

@bygui86 I'm a little confuse now :D --- > The event in ArgoEvents are duplicated because webhhoks are duplicated at creation time by Argo Events EventSource. > There is no...

@paolocarta @bygui86 Thank you! I can understand. Let's me take a look Maybe relate with this https://github.com/argoproj/argo-events/blob/f875e4212e738d096b4030e842fd34ae093374b3/eventsources/sources/gitlab/start.go#L291

@whynowy I'm thinking about something like mutex lock, so only one server will do creating hook job. What do you think?

> @sonbui00 can you please remove the stable? it's still relevant! @bygui86 Sorry, I don't have the permission to do @whynowy Could you help with this?

@agilgur5 Should I do anything to go forward for this?

@juliev0 I'll check it

@juliev0 codegen and lint issues have been fixed. help me review