João Duarte

This is because simpledateformat isn't thread safe and DateTimeFormatter should be used instead (read more [here](https://www.callicoder.com/java-simpledateformat-thread-safety-issues/)) "Offending" code is here https://github.com/guyboertje/jrjackson/blob/master/src/main/java/com/jrjackson/RubyAnySerializer.java#L233-L245

Logstash packages already have header and payload sha256 payloads: ``` ❯ rpm --checksig --verbose logstash-8.5.3-x86_64.rpm | grep SHA Header V4 RSA/SHA512 Signature, key ID d88e42b4: OK Header SHA256 digest: OK...

Recent 7.17.* Logstash RPMs already have the payload digest, ``` ❯ rpm --checksig --verbose /Users/joaoduarte/Downloads/logstash-7.17.5-x86_64.rpm Header V4 RSA/SHA512 Signature, key ID d88e42b4: OK Header SHA1 digest: OK V4 RSA/SHA512 Signature,...

wrt digest mismatch, Logstash artifact tasks aren't setting the `_binary_filedigest_algorithm` value to build RPMs, so by default it's MD5, which isn't accepted when FIPS is enabled in RHEL. Building a...

The simpest reproduction I could find was: ``` ❯ jruby -v jruby 9.4.3.0 (3.1.4) 2023-06-07 3086960792 OpenJDK 64-Bit Server VM 17.0.4.1+1 on 17.0.4.1+1 +jit [arm64-darwin] ❯ jruby -e "java.lang.Integer" -e:1:...

> This has been fixed or perhaps mitigated (perhaps someone can tell me): I can confirm that JRuby 9.4.6.0-SNAPSHOT won't show the to_int/to_f warnings on our use case (Logstash).

Related issues: * https://github.com/elastic/logstash/issues/5593 * https://github.com/elastic/logstash/issues/11917

It really shows the amount of effort put into this, it's much appreciated. a) I'd be nice to have a sample (manually constructed) json response from this API to help...

@mbudge thanks for the report. The challenge of deciding when to retry or not has been a back and forth for ages in Logstash, with arguments on both sides. The...

I kicked off exhaustive tests here: https://buildkite.com/elastic/logstash-exhaustive-tests-pipeline/builds/396