Karol Bucek

the JRuby 9.3 upgrade was shipped at https://github.com/elastic/logstash/pull/14114 (we expect this issue to be resolved in Logstash >= 8.3.0)

Thanks for the report, this sounds like a [plugin specific issue](https://github.com/logstash-plugins/logstash-output-syslog/issues). The syslog output uses UDP by default and seems to be opinionated about [re-trying exceptions when a `write` on...

> `:exception=>#` those exceptions are going to be retried by the output until a connection is possible - the event in that case is not ack-ed for the PQ and...

one more PR: https://github.com/puma/puma/pull/2899

and another PR: https://github.com/puma/puma/pull/2904

Hey, thanks for your interest in building an alternative to the existing pubsub input/output plugins. First of all the existing plugins while looking like Ruby are relatively thin wrappers and...

Sorry about the mess at some point Logstash core stopped pushing it's internals to RubyGems.org and some of the plugin dependencies expect a fairly recent logstash-core gem, these are always...

LGTM but I think we can showcase all the cases - here's something that I had in mind: > The behavior can easily be validated with this logstash configuration file:...

I do not think the original issue is relevant here - should be closed. there's a bug and the plugin repo: https://github.com/logstash-plugins/logstash-input-twitter/issues/74 I think given this is breaking for the...

@endorama the story is in general that TLS 1.3 support depends plugin by plugin and also the JDK used (in case of old LS versions or running on older Java...