profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/VaibhavPage/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Vaibhav VaibhavPage BlackRock USA

argoproj/argo-events 981

Event-driven workflow automation framework

argoproj/argo-helm 310

ArgoProj Helm Charts

ocibuilder/examples 3

Some examples of how to use ocibuilder

VaibhavPage/addon-manager 0

Manage addons in a Kubernetes cluster

VaibhavPage/advanced-go-programming-book 0

:books: 《Go语言高级编程》开源图书,涵盖CGO、Go汇编语言、RPC实现、Protobuf插件实现、Web框架实现、分布式系统等高阶主题(完稿)

VaibhavPage/amazon-eks-workshop 0

Amazon EKS workshop

issue commentargoproj/argo-events

EventSource and Sensor for multiple Github Repos

This issue has been automatically marked as stale because it has not had any activity in the last 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

ryanli-me

comment created time in 2 hours

issue openedargoproj/argo-events

Kafka/SASL password only configuration doesn't work

Config validation for Kafka/SAML is broken, when configuring just a password the contoller throws the following error:

{"level":"error","ts":1621011775.476398,"logger":"argo-events.eventsource-controller","caller":"eventsource/controller.go:81","msg":"validation error","namespace":"argo-events","eventSource":"kafka","error":"invalid sasl config, please configure either User, and/or Password"

This config works:

     sasl:
        mechanism: PLAIN
        password:
          key: password
          name: my-user
        user:
          key: user
          name: my-user```

This will not:
 sasl:
    mechanism: PLAIN
    password:
      key: password
      name: my-user```

created time in 11 hours

MemberEvent
MemberEvent

issue openedargoproj/argo-events

Better naming for default value of parameters and relevant doc refine

Is your feature request related to a problem? Please describe.

  1. Default value of a parameter can be specified with a key value, it's better to use a key like default;
  2. Dedicated docs for parameters feature instead of only can be found in the tutorials.

created time in a day

pull request commentargoproj/argo-events

chore: Dockerfile compatible with all Architecture builds

I see. It's Github actions. It has only x86 hosts available, so everything else is emulated, and takes ages to compile. I'll dig and see if I can achieve something. in the meantime, I have published the multmanifest image on my repo for anyone who needs docker.io/mickkael/argo-events:latest

mickkael

comment created time in 2 days

issue commentargoproj/argo-events

Kafka event source: no active event server running

The failure should be because the partition ID is not available. However, it's an issue that the error is not printed out.

MadDoxXimba

comment created time in 2 days

pull request commentargoproj/argo-events

chore: Dockerfile compatible with all Architecture builds

I'll work on the pipeline to make a multi-arch container. I do it already locally with an argo workflow and steps for arm64/arm/amd64, and mplatform/manifest-tool to have the multi-arch manifest. But we need this Dockerfile anyway as a starting point for each architecture build.

Hey @whynowy , what CI is used to build and push argo-events ? I can't find anything in the repo.

We used to support multi-arch build before, but there were some issues that pushing a large multi-arch image took too long and it often made the connection to image registry drop, so we removed that support. Now we have combined multiple images to one, I think probably we should get it back - but I'm not sure if the issue still exists, since current image is still large.

You could refer to https://github.com/argoproj/argo-events/pull/843.

The workflow to build images is https://github.com/argoproj/argo-events/blob/master/.github/workflows/release.yml.

mickkael

comment created time in 2 days

pull request commentargoproj/argo-events

chore: Dockerfile compatible with all Architecture builds

I'll work on the pipeline to make a multi-arch container. I do it already locally with an argo workflow and steps for arm64/arm/amd64, and mplatform/manifest-tool to have the multi-arch manifest. But we need this Dockerfile anyway as a starting point for each architecture build

mickkael

comment created time in 2 days

pull request commentargoproj/argo-events

chore: Dockerfile compatible with all Architecture builds

Thanks for your PR!

Instead of specifying the ARCH, I would expect to see it support multi-arch build automatically (#1190). Please let me know if you would like to take it.

mickkael

comment created time in 2 days

PR opened argoproj/argo-events

Dockerfile compatible with all Architecture builds

Signed-off-by: mickkael 19755421+mickkael@users.noreply.github.com

Compiled successfully arm64 with this patched Dockerfile https://hub.docker.com/r/mickkael/argo-events/tags

Checklist:

  • [ ] My organization is added to USERS.md.

<!--

Please leave your PR in draft if you don't need a review yet.

To fix failing CI / Codegen, run make codegen.

-->

+6 -4

0 comment

1 changed file

pr created time in 2 days

Pull request review commentargoproj/argo-events

fix: limit slack API calls

 func (t *SlackTrigger) Execute(ctx context.Context, events map[string]*v1alpha1.  	api := slack.New(slackToken, slack.OptionDebug(false)) -	params := &slack.GetConversationsParameters{-		Limit: 200,-		Types: []string{"public_channel", "private_channel"},-	}-	channelID := ""-	isPrivateChannel := false+	t.Logger.Infow("posting to channel...", zap.Any("channelName", channel)) 	for {-		channels, nextCursor, err := api.GetConversations(params)+		channelID, timestamp, err := api.PostMessage(channel, slack.MsgOptionText(message, false)) 		if err != nil {-			t.Logger.Errorw("unable to list channels", zap.Error(err))-			return nil, errors.Wrapf(err, "failed to list channels")-		}-		for _, c := range channels {-			if c.Name == channel {-				channelID = c.ID-				isPrivateChannel = c.IsPrivate-				break+			if err.Error() == "not_in_channel" {+				isPrivateChannel := false+				params := &slack.GetConversationsParameters{+					Limit:           200,+					Types:           []string{"public_channel", "private_channel"},+					ExcludeArchived: "true",+				}++				for {+					channels, nextCursor, err := api.GetConversations(params)+					if err != nil {+						switch e := err.(type) {+						case *slack.RateLimitedError:+							<-time.After(e.RetryAfter)+							continue+						default:+							t.Logger.Errorw("unable to list channels", zap.Error(err))+							return nil, errors.Wrapf(err, "failed to list channels")+						}+					}+					for _, c := range channels {+						if c.Name == channel {+							channelID = c.ID+							isPrivateChannel = c.IsPrivate+							break+						}+					}+					if nextCursor == "" || channelID != "" {

👍

tinkerborg

comment created time in 2 days

Pull request review commentargoproj/argo-events

fix: limit slack API calls

 func (t *SlackTrigger) Execute(ctx context.Context, events map[string]*v1alpha1.  	api := slack.New(slackToken, slack.OptionDebug(false)) -	params := &slack.GetConversationsParameters{-		Limit: 200,-		Types: []string{"public_channel", "private_channel"},-	}-	channelID := ""-	isPrivateChannel := false+	t.Logger.Infow("posting to channel...", zap.Any("channelName", channel)) 	for {-		channels, nextCursor, err := api.GetConversations(params)+		channelID, timestamp, err := api.PostMessage(channel, slack.MsgOptionText(message, false))

With the code change, do we still need the for loop in line 119? I seems to be infinite.

tinkerborg

comment created time in 2 days

Pull request review commentargoproj/argo-events

fix: limit slack API calls

 func (t *SlackTrigger) Execute(ctx context.Context, events map[string]*v1alpha1.  	api := slack.New(slackToken, slack.OptionDebug(false)) -	params := &slack.GetConversationsParameters{-		Limit: 200,-		Types: []string{"public_channel", "private_channel"},-	}-	channelID := ""-	isPrivateChannel := false+	t.Logger.Infow("posting to channel...", zap.Any("channelName", channel)) 	for {-		channels, nextCursor, err := api.GetConversations(params)+		channelID, timestamp, err := api.PostMessage(channel, slack.MsgOptionText(message, false)) 		if err != nil {-			t.Logger.Errorw("unable to list channels", zap.Error(err))-			return nil, errors.Wrapf(err, "failed to list channels")-		}-		for _, c := range channels {-			if c.Name == channel {-				channelID = c.ID-				isPrivateChannel = c.IsPrivate-				break+			if err.Error() == "not_in_channel" {+				isPrivateChannel := false+				params := &slack.GetConversationsParameters{+					Limit:           200,+					Types:           []string{"public_channel", "private_channel"},+					ExcludeArchived: "true",+				}++				for {+					channels, nextCursor, err := api.GetConversations(params)+					if err != nil {+						switch e := err.(type) {+						case *slack.RateLimitedError:+							<-time.After(e.RetryAfter)+							continue+						default:+							t.Logger.Errorw("unable to list channels", zap.Error(err))+							return nil, errors.Wrapf(err, "failed to list channels")+						}+					}+					for _, c := range channels {+						if c.Name == channel {+							channelID = c.ID+							isPrivateChannel = c.IsPrivate+							break+						}+					}+					if nextCursor == "" || channelID != "" {+						break+					}+					params.Cursor = nextCursor+				}+				if channelID == "" {+					return nil, errors.Errorf("failed to get channelID of %s", channel)+				}+				if isPrivateChannel {

I actually not very sure what the logic for private channel should be, but here the logic seems to be changed.

Old: Skip "join conversation", still post message; New: return an error.

tinkerborg

comment created time in 2 days

issue commentargoproj/argo-events

Kafka event source: no active event server running

I update the issue, the sensor problem was because of insufficient default RBAC permission over argo-worflow-sa service account.

MadDoxXimba

comment created time in 3 days

issue openedargoproj/argo-events

Kafka event source: no active event server running and Kafka sensor: does not dispatch

Describe the bug

Hi, i'm testing out the kafka event source and kafka sensor examples: https://argoproj.github.io/argo-events/eventsources/setup/kafka.

Event Source

{"level":"info","ts":1620814014.4780571,"logger":"argo-events.eventsource","caller":"cmd/main.go:63","msg":"starting eventsource server","eventSourceName":"kafka","version":"vv1.3.0+7591146.dirty"}
{"level":"info","ts":1620814014.4782612,"logger":"argo-events.eventsource","caller":"metrics/metrics.go:172","msg":"starting metrics server","eventSourceName":"kafka"}
{"level":"info","ts":1620814014.4810283,"logger":"argo-events.eventsource","caller":"leaderelection/leaderelection.go:122","msg":"Not the LEADER, stand by ...","eventSourceName":"kafka"}
{"level":"info","ts":1620814015.3544254,"logger":"argo-events.eventsource","caller":"leaderelection/leaderelection.go:131","msg":"Becoming a Candidate, stand by ...","eventSourceName":"kafka"}
{"level":"info","ts":1620814015.355255,"logger":"argo-events.eventsource","caller":"leaderelection/leaderelection.go:128","msg":"I'm the LEADER, starting ...","eventSourceName":"kafka"}
{"level":"info","ts":1620814015.3553903,"logger":"argo-events.eventsource","caller":"eventsources/eventing.go:309","msg":"Starting event source server...","eventSourceName":"kafka"}
{"level":"info","ts":1620814015.3563788,"logger":"argo-events.eventsource","caller":"driver/nats.go:93","msg":"NATS auth strategy: Token","eventSourceName":"kafka","clientID":"client-kafka-eventsource-g984s-58ff45bb8d-qpdgl-302"}
{"level":"info","ts":1620814015.3588736,"logger":"argo-events.eventsource","caller":"driver/nats.go:105","msg":"Connected to NATS server.","eventSourceName":"kafka","clientID":"client-kafka-eventsource-g984s-58ff45bb8d-qpdgl-302"}
{"level":"info","ts":1620814015.3620908,"logger":"argo-events.eventsource","caller":"driver/nats.go:118","msg":"Connected to NATS streaming server.","eventSourceName":"kafka","clientID":"client-kafka-eventsource-g984s-58ff45bb8d-qpdgl-302"}
{"level":"info","ts":1620814015.3621883,"logger":"argo-events.eventsource","caller":"eventsources/eventing.go:422","msg":"Eventing server started.","eventSourceName":"kafka"}
{"level":"info","ts":1620814015.3622308,"logger":"argo-events.eventsource","caller":"eventsources/eventing.go:332","msg":"starting eventbus connection daemon...","eventSourceName":"kafka"}
{"level":"info","ts":1620814015.362501,"logger":"argo-events.eventsource","caller":"kafka/start.go:78","msg":"start kafka event source...","eventSourceName":"kafka","eventSourceType":"kafka","eventName":"example"}
{"level":"info","ts":1620814015.3625581,"logger":"argo-events.eventsource","caller":"kafka/start.go:161","msg":"start kafka event source...","eventSourceName":"kafka","eventSourceType":"kafka","eventName":"example"}
{"level":"info","ts":1620814015.3625734,"logger":"argo-events.eventsource","caller":"kafka/start.go:165","msg":"connecting to Kafka cluster...","eventSourceName":"kafka","eventSourceType":"kafka","eventName":"example"}
{"level":"info","ts":1620814015.389459,"logger":"argo-events.eventsource","caller":"kafka/start.go:186","msg":"parsing the partition value...","eventSourceName":"kafka","eventSourceType":"kafka","eventName":"example","partition-id":"1"}
{"level":"info","ts":1620814015.3895614,"logger":"argo-events.eventsource","caller":"kafka/start.go:193","msg":"getting available partitions...","eventSourceName":"kafka","eventSourceType":"kafka","eventName":"example","partition-id":"1"}
{"level":"info","ts":1620814015.6654599,"logger":"argo-events.eventsource","caller":"kafka/start.go:199","msg":"verifying the partition exists within available partitions...","eventSourceName":"kafka","eventSourceType":"kafka","eventName":"example","partition-id":"1"}
{"level":"error","ts":1620814015.6655567,"logger":"argo-events.eventsource","caller":"eventsources/eventing.go:439","msg":"Erroring out, no active event server running","eventSourceName":"kafka","stacktrace":"github.com/argoproj/argo-events/eventsources.(*EventSourceAdaptor).run\n\t/home/runner/work/argo-events/argo-events/eventsources/eventing.go:439\ngithub.com/argoproj/argo-events/eventsources.(*EventSourceAdaptor).Start.func1\n\t/home/runner/work/argo-events/argo-events/eventsources/eventing.go:295"}
{"level":"info","ts":1620814015.665716,"logger":"argo-events.eventsource","caller":"eventsources/eventing.go:337","msg":"exiting eventbus connection daemon...","eventSourceName":"kafka"}
{"level":"error","ts":1620814015.6686988,"logger":"argo-events.eventsource","caller":"driver/nats.go:84","msg":"NATS connection lost","eventSourceName":"kafka","clientID":"client-kafka-eventsource-g984s-58ff45bb8d-qpdgl-302","stacktrace":"github.com/argoproj/argo-events/eventbus/driver.(*natsStreaming).Connect.func1\n\t/home/runner/work/argo-events/argo-events/eventbus/driver/nats.go:84\ngithub.com/nats-io/nats%2ego.(*Conn).close.func1\n\t/home/runner/go/pkg/mod/github.com/nats-io/nats.go@v1.10.0/nats.go:3802\ngithub.com/nats-io/nats%2ego.(*asyncCallbacksHandler).asyncCBDispatcher\n\t/home/runner/go/pkg/mod/github.com/nats-io/nats.go@v1.10.0/nats.go:2082"}
{"level":"error","ts":1620814015.6687121,"logger":"argo-events.eventsource","caller":"eventsources/eventing.go:296","msg":"failed to start","eventSourceName":"kafka","error":"no active event server running","errorVerbose":"no active event server running\ngithub.com/argoproj/argo-events/eventsources.(*EventSourceAdaptor).run\n\t/home/runner/work/argo-events/argo-events/eventsources/eventing.go:442\ngithub.com/argoproj/argo-events/eventsources.(*EventSourceAdaptor).Start.func1\n\t/home/runner/work/argo-events/argo-events/eventsources/eventing.go:295\nruntime.goexit\n\t/opt/hostedtoolcache/go/1.14.15/x64/src/runtime/asm_amd64.s:1373","stacktrace":"github.com/argoproj/argo-events/eventsources.(*EventSourceAdaptor).Start.func1\n\t/home/runner/work/argo-events/argo-events/eventsources/eventing.go:296"}

Sensor

Does not dispatch:

Name:         kafka
Namespace:    kast
Labels:       <none>
Annotations:  <none>
API Version:  argoproj.io/v1alpha1
Kind:         Sensor
Metadata:
  Creation Timestamp:  2021-05-12T10:40:34Z
  Finalizers:
    sensor-controller
  Generation:  1
  Managed Fields:
    API Version:  argoproj.io/v1alpha1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .:
          f:kubectl.kubernetes.io/last-applied-configuration:
      f:spec:
        .:
        f:dependencies:
        f:template:
        f:triggers:
    Manager:      kubectl-client-side-apply
    Operation:    Update
    Time:         2021-05-12T10:40:34Z
    API Version:  argoproj.io/v1alpha1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:finalizers:
          .:
          v:"sensor-controller":
      f:status:
        .:
        f:conditions:
    Manager:         sensor-controller
    Operation:       Update
    Time:            2021-05-12T10:40:34Z
  Resource Version:  2812
  UID:               995b1b94-ca80-4976-8df1-062b984b7981
Spec:
  Dependencies:
    Event Name:         example
    Event Source Name:  kafka
    Name:               test-dep
  Template:
    Service Account Name:  operate-workflow-sa
  Triggers:
    Template:
      k8s:
        Group:      argoproj.io
        Operation:  create
        Parameters:
          Dest:  spec.arguments.parameters.0.value
          Src:
            Dependency Name:  test-dep
        Resource:             workflows
        Source:
          Resource:
            API Version:  argoproj.io/v1alpha1
            Kind:         Workflow
            Metadata:
              Generate Name:  kafka-workflow-
            Spec:
              Arguments:
                Parameters:
                  Name:    message
                  Value:   hello world
              Entrypoint:  whalesay
              Templates:
                Container:
                  Args:
                    {{inputs.parameters.message}}
                  Command:
                    cowsay
                  Image:  docker/whalesay:latest
                Inputs:
                  Parameters:
                    Name:  message
                Name:      whalesay
        Version:           v1alpha1
      Name:                kafka-workflow-trigger
Status:
  Conditions:
    Last Transition Time:  2021-05-12T10:40:34Z
    Status:                True
    Type:                  DependenciesProvided
    Last Transition Time:  2021-05-12T10:40:34Z
    Status:                True
    Type:                  Deployed
    Last Transition Time:  2021-05-12T10:40:34Z
    Status:                True
    Type:                  TriggersProvided
Events:                    <none>

controller logs

{"level":"info","ts":1620813891.9073696,"logger":"argo-events.sensor-controller","caller":"cmd/main.go:135","msg":"starting sensor controller","version":"vv1.3.0+7591146.dirty"}
{"level":"info","ts":1620816034.977807,"logger":"argo-events.sensor-controller","caller":"sensor/resource.go:107","msg":"deployment is created","namespace":"kast","sensor":"kafka","deploymentName":"kafka-sensor-hvqbn"}

To Reproduce Steps to reproduce the behavior:

Used minikube as POC environment.

Kafka installation

https://strimzi.io/docs/operators/in-development/quickstart.html#assembly-evaluation-str

Tried on argo-events and eventbus:

  • namespace installation
  • cluster-wide installation

Expected behavior Events are published to event source and kafka sensor is dispatched

Screenshots

  1. missing kafka sensor pod
  2. wrong status for kafka-eventsource?
$ kubectl get pods

NAME                                       READY   STATUS    RESTARTS   AGE
argo-server-6fb6d4b7fb-2lq5l               1/1     Running   0          8m19s
eventbus-controller-96f86d586-nd52t        1/1     Running   0          8m33s
eventbus-default-stan-0                    2/2     Running   0          8m21s
eventbus-default-stan-1                    2/2     Running   0          8m6s
eventbus-default-stan-2                    2/2     Running   0          8m4s
eventsource-controller-5b9b5dd4b-6t96h     1/1     Running   0          8m33s
kafka-eventsource-97lqq-7f9dc97bfc-8gjtt   1/1     Running   0          5m54s
sensor-controller-77dbfb77bf-4hn8j         1/1     Running   0          8m33s
workflow-controller-d9cbfcc86-l2r8v        1/1     Running   0          8m19s

Environment (please complete the following information):

  • Minikube: v1.18.1
  • Argo: v3.0.2
  • Argo Events: v1.3.0 v1.3.1

Additional context Add any other context about the problem here.


<!-- Issue Author: Don't delete this message to encourage other users to support your issue! --> Message from the maintainers:

If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

created time in 3 days

pull request commentargoproj/argo-events

fix: limit slack API calls

Not any particular test case. I only tested if the message is posted in private channel. In your case you told that it is working after your code changes, so it should be fine. Don't think if anymore scenarios required.

tinkerborg

comment created time in 3 days

pull request commentargoproj/argo-events

fix: limit slack API calls

@shashwat-appdirect Using my bot's token in the API tester, with private_channel argument, I can list private channels, but only the ones to which my bot has already been invited. So it's still not clear to me what the isPrivateChannel logic was doing.

conversations.join is not allowed for a private channel. Earlier if the channel was found in conversations.list, the conversations.join method was still called. But if the channel is private, this method fails with error - method_not_supported_for_channel_type. Hence, to avoid calling this method on private channels, isPrivateChannel check was used. You could go through the old code flow, if still it is not clear :)

I didn't change this flow, just moved it to after trying chat.postMessage, and added the rate limiting. I don't see that it is doing anything though, since conversations.list only lists private channels if the bot is already joined. If you have a test case that the previous PR was addressing, I can try to reproduce and test with the code in this PR.

tinkerborg

comment created time in 3 days

pull request commentargoproj/argo-events

fix: limit slack API calls

@shashwat-appdirect Using my bot's token in the API tester, with private_channel argument, I can list private channels, but only the ones to which my bot has already been invited. So it's still not clear to me what the isPrivateChannel logic was doing.

conversations.join is not allowed for a private channel. Earlier if the channel was found in conversations.list, the conversations.join method was still called. But if the channel is private, this method fails with error - method_not_supported_for_channel_type. Hence, to avoid calling this method on private channels, isPrivateChannel check was used. You could go through the old code flow, if still it is not clear :)

tinkerborg

comment created time in 3 days

issue commentargoproj/argo-events

Customise the Github Event for Argo Events

This issue has been automatically marked as stale because it has not had any activity in the last 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

avinashkumar1289

comment created time in 3 days

pull request commentargoproj/argo-events

chore: Combine binaries/images to one

quay.io/argoproj/argo-events images are not available.

Now it is.

whynowy

comment created time in 3 days

pull request commentargoproj/argo-events

chore: Combine binaries/images to one

quay.io/argoproj/argo-events images are not available.

whynowy

comment created time in 3 days

pull request commentargoproj/argo-events

fix: limit slack API calls

@shashwat-appdirect Using my bot's token in the API tester, with private_channel argument, I can list private channels, but only the ones to which my bot has already been invited. So it's still not clear to me what the isPrivateChannel logic was doing.

tinkerborg

comment created time in 3 days

pull request commentargoproj/argo-events

fix: limit slack API calls

I am sure earlier conversations.list returned both public and private channels. To get private channel you need to pass private_channel in the field types, while calling conversations.list method. I tested just now using Slack API Tester - https://api.slack.com/methods/conversations.list/test and able to list all public and private channels.

That was my understanding as well, otherwise why would the option even exist? I'll do some digging and see if I can figure out what's going on.

tinkerborg

comment created time in 3 days

push eventargoproj/argo-events

whynowy

commit sha aee46a1e4366490fc42baa6e4405d224df129187

deploy: c8e2dfd73adc248645685fc84b9d0b4e6d69dd00

view details

push time in 3 days

push eventargoproj/argo-events

Derek Wang

commit sha c8e2dfd73adc248645685fc84b9d0b4e6d69dd00

fix(ci): fix env name for quay.io (#1211) * fix(ci): correct env name for quay.io Signed-off-by: Derek Wang <whynowy@gmail.com>

view details

push time in 3 days

PR merged argoproj/argo-events

fix(ci): fix env name for quay.io

Signed-off-by: Derek Wang whynowy@gmail.com

Checklist:

  • [ ] My organization is added to USERS.md.

<!--

Please leave your PR in draft if you don't need a review yet.

To fix failing CI / Codegen, run make codegen.

-->

+1 -1

0 comment

1 changed file

whynowy

pr closed time in 3 days

PR opened argoproj/argo-events

fix(ci): correct env name for quay.io

Signed-off-by: Derek Wang whynowy@gmail.com

Checklist:

  • [ ] My organization is added to USERS.md.

<!--

Please leave your PR in draft if you don't need a review yet.

To fix failing CI / Codegen, run make codegen.

-->

+1 -1

0 comment

1 changed file

pr created time in 3 days

push eventargoproj/argo-events

whynowy

commit sha b132c681ecd95c922fdb8a299735073c4cd9e2fb

deploy: 8449ddbecea40cab2db755024cac652faaac07c6

view details

push time in 3 days

push eventargoproj/argo-events

Derek Wang

commit sha 8449ddbecea40cab2db755024cac652faaac07c6

chore: Combine binaries/images to one (#1203) * chore: Combine binaries/images to one Signed-off-by: Derek Wang <whynowy@gmail.com>

view details

push time in 3 days