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

Propagate connect_timeout argument to kpro API functions #458

Merged
merged 1 commit into from
Feb 5, 2022

Conversation

hairyhum
Copy link
Contributor

A number of kpro connection functions support a timeout argument
which is not provided by brod functions.
This makes it use a default timeout of 5 seconds.

Make sure brod and brod_utils functions use
the connect_timeout client config for this argument

@zmstone
Copy link
Contributor

zmstone commented May 26, 2021

thank you for the PR @hairyhum
could you help to update changelog.md ? make it 3.15.5

@hairyhum hairyhum force-pushed the kpro-connection-timeout branch from 9eeba9a to fb928ed Compare May 26, 2021 23:21
@hairyhum hairyhum changed the title Add propagate connect_timeout argument to kpro API functions Propagate connect_timeout argument to kpro API functions May 27, 2021
@zmstone
Copy link
Contributor

zmstone commented Jul 7, 2021

Hi @hairyhum
there were few issues with CI which has been fixed.
Could you please rebase on the latest master?

@hairyhum hairyhum force-pushed the kpro-connection-timeout branch from fb928ed to d70fc87 Compare October 22, 2021 16:39
…t` arg

A number of kpro connection functions support a timeout argument
which is not provided by brod functions.
This makes it use a default timeout of 5 seconds.

Make sure brod and brod_utils functions use
the connect_timeout client config for this argument
@hairyhum hairyhum force-pushed the kpro-connection-timeout branch from d70fc87 to 3e4f590 Compare November 3, 2021 20:41
@zmstone zmstone merged commit a9c193c into kafka4beam:master Feb 5, 2022
@zmstone
Copy link
Contributor

zmstone commented Feb 5, 2022

sorry for the delay.

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.

2 participants