Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Dec 17, 2025

The latest psych 5.3 minor version has bumped snakeyaml-engine ruby/psych#762. This is causing issues in bundler. Constrain the psych gem to the 5.2 minor version while we are still on jruby 9.4.13.0.

The issue presents as:

Errno::ENOENT: No such file or directory - /Users/cas/elastic-repos/logstash/vendor/jruby/lib/ruby/gems/shared/gems/psych-5.3.1-java/deps.lst
  org/jruby/RubyIO.java:1279:in `sysopen'
          org/jruby/RubyIO.java:4275:in `read'
          /Users/cas/elastic-repos/logstash/vendor/jruby/lib/ruby/stdlib/jars/installer.rb:75:in `load_from_maven'
          /Users/cas/elastic-repos/logstash/vendor/jruby/lib/ruby/stdlib/jars/installer.rb:220:in `install_dependencies'
          /Users/cas/elastic-repos/logstash/vendor/jruby/lib/ruby/stdlib/jars/installer.rb:209:in `do_install'
          /Users/cas/elastic-repos/logstash/vendor/jruby/lib/ruby/stdlib/jars/installer.rb:154:in `vendor_jars'
          /Users/cas/elastic-repos/logstash/vendor/jruby/lib/ruby/stdlib/rubygems/defaults/jruby.rb:110:in `block in <main>'
          /Users/cas/elastic-repos/logstash/vendor/jruby/lib/ruby/stdlib/rubygems/installer.rb:367:in `block in run_post_install_hooks'
          org/jruby/RubyArray.java:2009:in `each'
          /Users/cas/elastic-repos/logstash/vendor/jruby/lib/ruby/stdlib/rubygems/installer.rb:366:in `run_post_install_hooks'
          /Users/cas/elastic-repos/logstash/vendor/jruby/lib/ruby/stdlib/bundler/rubygems_gem_installer.rb:48:in `install'
          /Users/cas/elastic-repos/logstash/vendor/jruby/lib/ruby/stdlib/bundler/source/rubygems.rb:205:in `install'
          /Users/cas/elastic-repos/logstash/vendor/jruby/lib/ruby/stdlib/bundler/installer/gem_installer.rb:55:in `install'
          /Users/cas/elastic-repos/logstash/vendor/jruby/lib/ruby/stdlib/bundler/installer/gem_installer.rb:17:in `install_from_spec'
          /Users/cas/elastic-repos/logstash/vendor/jruby/lib/ruby/stdlib/bundler/installer/parallel_installer.rb:133:in `do_install'
          /Users/cas/elastic-repos/logstash/vendor/jruby/lib/ruby/stdlib/bundler/installer/parallel_installer.rb:124:in `block in worker_pool'
          /Users/cas/elastic-repos/logstash/vendor/jruby/lib/ruby/stdlib/bundler/worker.rb:62:in `apply_func'
          /Users/cas/elastic-repos/logstash/vendor/jruby/lib/ruby/stdlib/bundler/worker.rb:57:in `block in process_queue'
          org/jruby/RubyKernel.java:1725:in `loop'
          /Users/cas/elastic-repos/logstash/vendor/jruby/lib/ruby/stdlib/bundler/worker.rb:54:in `process_queue'
          /Users/cas/elastic-repos/logstash/vendor/jruby/lib/ruby/stdlib/bundler/worker.rb:90:in `block in create_threads'

There has been a long standing string of issues around this:

The current issue seems to be that when psych depends on a different version of snakeyaml-engine that is shipped in jruby (Logstash is on 9.4.13.0 which vendors snakeyaml-engine 2.9).


This is an automatic backport of pull request #18507 done by Mergify.

The latest psych 5.3 minor version has bumped snakeyaml-engine
ruby/psych#762. This is causing issues in bundler.
Constrain the psych gem to the 5.2 minor version while we are still on jruby
9.4.13.0.

(cherry picked from commit a089904)
@github-actions
Copy link
Contributor

🤖 GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)
  • /run exhaustive tests : Run the exhaustive tests Buildkite pipeline.

Copy link
Contributor

@mashhurs mashhurs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@elasticmachine
Copy link

💛 Build succeeded, but was flaky

Failed CI Steps

cc @donoghuc

@mashhurs mashhurs merged commit a55bc73 into 9.3 Dec 17, 2025
14 checks passed
@mashhurs mashhurs deleted the mergify/bp/9.3/pr-18507 branch December 17, 2025 21:11
donoghuc added a commit that referenced this pull request Dec 18, 2025
mashhurs pushed a commit that referenced this pull request Dec 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants