Closed motymichaely closed 3 years ago
Any chance we can get a release cut? Running into this issue with 1.1.0
.
Is master working for you?
On Sat, Nov 13, 2021 at 11:23 Christopher J. Bottaro < @.***> wrote:
Any chance we can get a release cut? Running into this issue with 1.1.0.
— You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/contribsys/faktory_worker_ruby/issues/59#issuecomment-968122088, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAAWX7L363OVPNSWYWVOJDUL23M5ANCNFSM47BDPYPQ .
Yup!
10-4, expect 1.1 next week.
On Sat, Nov 13, 2021 at 11:26 Christopher J. Bottaro < @.***> wrote:
Yup!
— You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/contribsys/faktory_worker_ruby/issues/59#issuecomment-968122563, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAAWX6VB3OGKS7DFPPFXRLUL23X5ANCNFSM47BDPYPQ .
v1.1.1 is out.
Faktory client fails to connect to Faktory server behind AWS Network Load Blanacer with TLS listener.
Establishing a simple Faktory client connection to a Faktory server behind an AWS Network Load Balancer with TLS listener fails:
The stacktrace:
NOTE: Establishing the same connection using Go client and Python client works as expected.
Gemfile:
Gemfile.lock: