João Duarte

@jagan2221 sweet, thanks for the interest! as I was waiting for a sponsor I ended up writing a lot of code, which includes the dns lookups as a source, which...

/run exhaustive tests

this feature request aside, I must remind that multiple pipelines are compatible with the dynamic config reloading. so if logstash is started with `-r`, adding/removing a new entry to the...

@fbaligand it will stop the pipeline and delete it internally, uncommenting will add and start it

@donoghuc after some tests, I agree that we can't delete all of stdlib and there will have to be a compromise between just deleting gemspecs and some ruby deletions as...

I am not opposed to doing it at that stage, my rationale for doing it asap was to ensure that anything on top of the vendored jruby HAD to live...

@donoghuc after a ridiculous amount of time digging into rubygems and bundler, I can see why prefer-local is giving us problems, looking at the [changelog for 2.6.4](https://github.com/ruby/rubygems/blob/bundler-v2.6.9/bundler/CHANGELOG.md#264-february-17-2025) (JRuby 9.4.13.0 ships...

I ended up with a rather complicated changeset: https://github.com/elastic/logstash/commit/00ee944e6a50fcaca5a8ca7a311be66dfb36de5a It reduces the total gemspec to 479, from 485 of our PR18340~1 (i.e. without prefer-local) and from 513 in main. The...

> My hunch is that queueless will either have serious performance problems due to one-at-a-time processing or we will have to make significant API changes[1] to the Inputs to enable...

Gem duplication findings: Regarding gem duplication from artifacts I can see that removing all gems from `./vendor/jruby/lib/ruby/gems/shared/gems` and gemspecs from `./vendor/jruby/lib/ruby/gems/shared/specifications/`, but keeping only bundler and its gemspec doesn't hinder...