-
Notifications
You must be signed in to change notification settings - Fork 173
DBZ-7570/#133: add workaround using SO_LINGER with 0 timeout #142
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
DBZ-7570/#133: add workaround using SO_LINGER with 0 timeout #142
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR @acristu, I've left one comment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@osheroff, this LGTM as it's opt-in. Could you ping me when we have a public build of the binlog available? Thanks!
@Naros go ahead and make the pom.xml change + the CHANGELOG entry. I'll merge and release. I'd also like to just set you up with the credentials necessary to do releases of this repo yourself, although I can never remember the incantations required to give you access there... |
@osheroff Could you publish a new version? Latest version is still |
Whenever you do, just drop me a note to the email in my GitHub profile @osheroff . |
ok published after some shenannigans with sonatype. @Naros I spoke too soon, I don't think I can grant you access to publish under com.zendesk (I don't work there anymore). I guess we could cut the publishing over to redhat if you want to grant me access to publish the artifact, or... eh |
@osheroff would you be open to the idea of we fork this under the debezium umbrella and cut releases with our automated release processes, since this is a critical component for two of our connectors? |
Yeah that’s fine by me.On Jul 10, 2024, at 16:50, Chris Cranford ***@***.***> wrote:
@osheroff would you be open to the idea of we fork this under the debezium umbrella and cut releases with our automated release processes, since this is a critical component for two of our connectors?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
No description provided.