Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: adjust connection for custom gRPC trigger #3421

Merged
merged 1 commit into from
Jan 10, 2025

Conversation

mweibel
Copy link
Contributor

@mweibel mweibel commented Jan 10, 2025

grpc.NewClient does not automatically connect to the gRPC server anymore. This is unlike the previously used grpc.Dial1.

This change reintroduces initial connection test.

I'm unsure whether we should actually do this, but at least it makes the code work again.

fixes #3420.

Checklist:

`grpc.NewClient` does not automatically connect to the gRPC server
anymore. This is unlike the previously used `grpc.Dial`[1].

This change reintroduces initial connection test.

[1]: https://github.com/grpc/grpc-go/blob/master/Documentation/anti-patterns.md

Signed-off-by: Michael Weibel <[email protected]>
@mweibel mweibel requested a review from whynowy as a code owner January 10, 2025 13:00
Copy link
Member

@whynowy whynowy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing it!

@whynowy whynowy merged commit e4eaea5 into argoproj:master Jan 10, 2025
7 checks passed
whynowy pushed a commit that referenced this pull request Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Argo events 1.9.4 fails to open gRPC connection to custom trigger
2 participants