bump snakeyaml-engine to 2.10 (jruby) - #762

Merged
headius merged 1 commit into
ruby:masterfrom
kares:bump-snakeyaml-2.10
Dec 11, 2025
Merged

bump snakeyaml-engine to 2.10 (jruby)#762
headius merged 1 commit into
ruby:masterfrom
kares:bump-snakeyaml-2.10

Conversation

@kares

Copy link
Copy Markdown
Contributor

No description provided.

@headius
headius merged commit 5af4cec into ruby:masterDec 11, 2025
75 checks passed
@headius

Copy link
Copy Markdown
Contributor

Thanks @kares!

donoghuc added a commit to donoghuc/logstash that referenced this pull request 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.
@donoghuc

Copy link
Copy Markdown

@kares@headius Would we expect that the snakeyaml-engine for psych need to match the version vendored with jruby? For example when running psych 5.3.1 with jruby 9.4.13.0 (which ships with snakeyaml-engine 2.9) we are seeing issues with bundler (see elastic/logstash#18507 (comment))

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'

Seems related to the maven/jar-dependencies rabbit hole this points to #690

donoghuc added a commit to elastic/logstash that referenced this pull request 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.
mergifyBot pushed a commit to elastic/logstash that referenced this pull request 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.
(cherry picked from commit a089904)
mashhurs pushed a commit to elastic/logstash that referenced this pull request 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.
(cherry picked from commit a089904)
Co-authored-by: Cas Donoghue <cas.donoghue@gmail.com>
@kares

Copy link
Copy Markdown
ContributorAuthor

for the embedded use-case, Logstah is, this really is up to you to manage.

you can e.g. take on jar-deps to be better aligned with your use-case, unless the plan is to comment on every jar dependency bump on external gems.

@donoghuc

Copy link
Copy Markdown

It seems like with jruby 9.4.13.0 and bundler 2.6.3 at least, the issue is independent of logstash. For example:

For this Gemfile:

source "https://rubygems.org"
gem 'psych', '~> 5.3.1'

A bundle install gives this error:

Fetching gem metadata from https://rubygems.org/........
Resolving dependencies...
Fetching date 3.5.1 (java)
Installing date 3.5.1 (java)
Fetching psych 5.3.1 (java)
Installing psych 5.3.1 (java)
jar dependencies for psych-5.3.1-java.gemspec . . .
org.snakeyaml:snakeyaml-engine:2.10:compile
[ERROR] Failed to execute goal on project jars: Could not collect dependencies for project no_group_id_given:jars:jar:0.0.0
[ERROR] Failed to read artifact descriptor for org.snakeyaml:snakeyaml-engine:jar:2.10
[ERROR] Caused by: The following artifacts could not be resolved: org.snakeyaml:snakeyaml-engine:pom:2.10 (absent): Could not transfer artifact org.snakeyaml:snakeyaml-engine:pom:2.10 from/to central (https://repo.maven.apache.org/maven2): Operation timed out
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
--- ERROR REPORT TEMPLATE -------------------------------------------------------

Errno::ENOENT: No such file or directory - /Users/cas/.rbenv/versions/jruby-9.4.13.0/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/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:76:in load_from_maven' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:221:in install_dependencies'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:210:in do_install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:155:in vendor_jars'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/defaults/jruby.rb:110:in block in <main>' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/installer.rb:367:in block in run_post_install_hooks'
org/jruby/RubyArray.java:2009:in each' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/installer.rb:366:in run_post_install_hooks'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/rubygems_gem_installer.rb:48:in install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/source/rubygems.rb:205:in install'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/gem_installer.rb:55:in install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/gem_installer.rb:17:in install_from_spec'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/parallel_installer.rb:133:in do_install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/parallel_installer.rb:124:in block in worker_pool'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:62:in apply_func' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:57:in block in process_queue'
org/jruby/RubyKernel.java:1725:in loop' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:54:in process_queue'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:90:in `block in create_threads'


## Environment

Bundler 2.6.3
Platforms ruby, universal-java-21
Ruby 3.1.4p0 (2025-06-10 revision 9938a3461fbfdf6048dda0a0411551d6a433581a) [universal-java-21]
Full Path /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin/jruby
Config Dir /Users/cas/.rbenv/versions/jruby-9.4.13.0/etc
RubyGems 3.6.3
Gem Home /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared
Gem Path /Users/cas/.local/share/gem/jruby/3.1.0:/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared
User Home /Users/cas
User Path /Users/cas/.local/share/gem/jruby/3.1.0
Bin Dir /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin
OpenSSL
Compiled JRuby-OpenSSL 0.15.4
Loaded JRuby-OpenSSL 0.15.4
Cert File /opt/homebrew/Cellar/openjdk@21/21.0.6/libexec/openjdk.jdk/Contents/Home/lib/security/cacerts
Cert Dir /etc/ssl/certs
Tools
Git 2.47.0
RVM not installed
rbenv rbenv 1.3.2
chruby not installed
Gem.ruby /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin/jruby
bundle #! /usr/bin/env jruby


## Bundler Build Metadata

Built At 2025-01-16
Git SHA 3c7c4ff2d8f
Released Version true


## Gemfile
### Gemfile
```ruby
source "https://rubygems.org"
gem 'psych', '~> 5.3.1'

Gemfile.lock

<No /private/tmp/bar/Gemfile.lock found>

--- TEMPLATE END ----------------------------------------------------------------

Unfortunately, an unexpected error occurred, and Bundler cannot continue.

First, try this link to see if there are any existing issue reports for this error:
https://github.com/rubygems/rubygems/search?q=No+such+file+or+directory+-+%2FUsers%2Fcas%2F.rbenv%2Fversions%2Fjruby-9.4.13.0%2Flib%2Fruby%2Fgems%2Fshared%2Fgems%2Fpsych-5.3.1-java%2Fdeps.lst&type=Issues

If there aren't any reports for this error yet, please fill in the new issue form located at https://github.com/rubygems/rubygems/issues/new?labels=Bundler&template=bundler-related-issue.md, and copy and paste the report template above in there.

@donoghuc

Copy link
Copy Markdown

Actually disregard that! Sorry, I had a local maven config that was using a broken proxy 🤦 Jar-dependencies is able to manage the snakeyaml-engine jar.

@chadlwilson

chadlwilson commented Dec 19, 2025

Copy link
Copy Markdown
Contributor

Yeah, this broke gocd too with the a similar error; except a file not found on the jar. I suspect there could be a bug in jar_dependencies, possibly when using an existing cached jar_dependencies alongside BUNDLE_GLOBAL_GEM_CACHE and JARS_SKIP in my case.

@donoghuc - did you have to do anything in particular with your proxy to "unbreak" it, in case my issue is that too?

@donoghuc

Copy link
Copy Markdown

@chadlwilson i found that setting the JARS_DEBUG=true and JARS_VERBOSE=true environment variables when doing the install helped explain exactly what the issue was. In my case i had a defunct proxy configured in my ~/.m2/settings.xml file.

One note that i found frustrating was that in the case I mentioned in this comment #762 (comment) the rest of the psych gem would install (just not the snakeyaml-engine jar) and then subsequent bundle installs would appear to succeed.

@chadlwilson

Copy link
Copy Markdown
Contributor

Thanks for the tips!

I noted something similar about the "appears to succeed" in jruby/jruby#8886 which is a related issue (the one I was trying to workaround with JARS_SKIP in the first place since I don't actually need psych, I just get it as a transitive). I imagine my setup is sufficiently different that my problems might be something different though.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@kares@headius@donoghuc@chadlwilson
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

bump snakeyaml-engine to 2.10 (jruby) - #762

Merged
headius merged 1 commit into
ruby:masterfrom
kares:bump-snakeyaml-2.10
Dec 11, 2025
Merged

bump snakeyaml-engine to 2.10 (jruby)#762
headius merged 1 commit into
ruby:masterfrom
kares:bump-snakeyaml-2.10

Conversation

@kares

Copy link
Copy Markdown
Contributor

No description provided.

@headius
headius merged commit 5af4cec into ruby:masterDec 11, 2025
75 checks passed
@headius

Copy link
Copy Markdown
Contributor

Thanks @kares!

donoghuc added a commit to donoghuc/logstash that referenced this pull request 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.
@donoghuc

Copy link
Copy Markdown

@kares@headius Would we expect that the snakeyaml-engine for psych need to match the version vendored with jruby? For example when running psych 5.3.1 with jruby 9.4.13.0 (which ships with snakeyaml-engine 2.9) we are seeing issues with bundler (see elastic/logstash#18507 (comment))

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'

Seems related to the maven/jar-dependencies rabbit hole this points to #690

donoghuc added a commit to elastic/logstash that referenced this pull request 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.
mergifyBot pushed a commit to elastic/logstash that referenced this pull request 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.
(cherry picked from commit a089904)
mashhurs pushed a commit to elastic/logstash that referenced this pull request 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.
(cherry picked from commit a089904)
Co-authored-by: Cas Donoghue <cas.donoghue@gmail.com>
@kares

Copy link
Copy Markdown
ContributorAuthor

for the embedded use-case, Logstah is, this really is up to you to manage.

you can e.g. take on jar-deps to be better aligned with your use-case, unless the plan is to comment on every jar dependency bump on external gems.

@donoghuc

Copy link
Copy Markdown

It seems like with jruby 9.4.13.0 and bundler 2.6.3 at least, the issue is independent of logstash. For example:

For this Gemfile:

source "https://rubygems.org"
gem 'psych', '~> 5.3.1'

A bundle install gives this error:

Fetching gem metadata from https://rubygems.org/........
Resolving dependencies...
Fetching date 3.5.1 (java)
Installing date 3.5.1 (java)
Fetching psych 5.3.1 (java)
Installing psych 5.3.1 (java)
jar dependencies for psych-5.3.1-java.gemspec . . .
org.snakeyaml:snakeyaml-engine:2.10:compile
[ERROR] Failed to execute goal on project jars: Could not collect dependencies for project no_group_id_given:jars:jar:0.0.0
[ERROR] Failed to read artifact descriptor for org.snakeyaml:snakeyaml-engine:jar:2.10
[ERROR] Caused by: The following artifacts could not be resolved: org.snakeyaml:snakeyaml-engine:pom:2.10 (absent): Could not transfer artifact org.snakeyaml:snakeyaml-engine:pom:2.10 from/to central (https://repo.maven.apache.org/maven2): Operation timed out
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
--- ERROR REPORT TEMPLATE -------------------------------------------------------

Errno::ENOENT: No such file or directory - /Users/cas/.rbenv/versions/jruby-9.4.13.0/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/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:76:in load_from_maven' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:221:in install_dependencies'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:210:in do_install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:155:in vendor_jars'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/defaults/jruby.rb:110:in block in <main>' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/installer.rb:367:in block in run_post_install_hooks'
org/jruby/RubyArray.java:2009:in each' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/installer.rb:366:in run_post_install_hooks'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/rubygems_gem_installer.rb:48:in install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/source/rubygems.rb:205:in install'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/gem_installer.rb:55:in install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/gem_installer.rb:17:in install_from_spec'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/parallel_installer.rb:133:in do_install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/parallel_installer.rb:124:in block in worker_pool'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:62:in apply_func' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:57:in block in process_queue'
org/jruby/RubyKernel.java:1725:in loop' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:54:in process_queue'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:90:in `block in create_threads'


## Environment

Bundler 2.6.3
Platforms ruby, universal-java-21
Ruby 3.1.4p0 (2025-06-10 revision 9938a3461fbfdf6048dda0a0411551d6a433581a) [universal-java-21]
Full Path /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin/jruby
Config Dir /Users/cas/.rbenv/versions/jruby-9.4.13.0/etc
RubyGems 3.6.3
Gem Home /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared
Gem Path /Users/cas/.local/share/gem/jruby/3.1.0:/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared
User Home /Users/cas
User Path /Users/cas/.local/share/gem/jruby/3.1.0
Bin Dir /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin
OpenSSL
Compiled JRuby-OpenSSL 0.15.4
Loaded JRuby-OpenSSL 0.15.4
Cert File /opt/homebrew/Cellar/openjdk@21/21.0.6/libexec/openjdk.jdk/Contents/Home/lib/security/cacerts
Cert Dir /etc/ssl/certs
Tools
Git 2.47.0
RVM not installed
rbenv rbenv 1.3.2
chruby not installed
Gem.ruby /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin/jruby
bundle #! /usr/bin/env jruby


## Bundler Build Metadata

Built At 2025-01-16
Git SHA 3c7c4ff2d8f
Released Version true


## Gemfile
### Gemfile
```ruby
source "https://rubygems.org"
gem 'psych', '~> 5.3.1'

Gemfile.lock

<No /private/tmp/bar/Gemfile.lock found>

--- TEMPLATE END ----------------------------------------------------------------

Unfortunately, an unexpected error occurred, and Bundler cannot continue.

First, try this link to see if there are any existing issue reports for this error:
https://github.com/rubygems/rubygems/search?q=No+such+file+or+directory+-+%2FUsers%2Fcas%2F.rbenv%2Fversions%2Fjruby-9.4.13.0%2Flib%2Fruby%2Fgems%2Fshared%2Fgems%2Fpsych-5.3.1-java%2Fdeps.lst&type=Issues

If there aren't any reports for this error yet, please fill in the new issue form located at https://github.com/rubygems/rubygems/issues/new?labels=Bundler&template=bundler-related-issue.md, and copy and paste the report template above in there.

@donoghuc

Copy link
Copy Markdown

Actually disregard that! Sorry, I had a local maven config that was using a broken proxy 🤦 Jar-dependencies is able to manage the snakeyaml-engine jar.

@chadlwilson

chadlwilson commented Dec 19, 2025

Copy link
Copy Markdown
Contributor

Yeah, this broke gocd too with the a similar error; except a file not found on the jar. I suspect there could be a bug in jar_dependencies, possibly when using an existing cached jar_dependencies alongside BUNDLE_GLOBAL_GEM_CACHE and JARS_SKIP in my case.

@donoghuc - did you have to do anything in particular with your proxy to "unbreak" it, in case my issue is that too?

@donoghuc

Copy link
Copy Markdown

@chadlwilson i found that setting the JARS_DEBUG=true and JARS_VERBOSE=true environment variables when doing the install helped explain exactly what the issue was. In my case i had a defunct proxy configured in my ~/.m2/settings.xml file.

One note that i found frustrating was that in the case I mentioned in this comment #762 (comment) the rest of the psych gem would install (just not the snakeyaml-engine jar) and then subsequent bundle installs would appear to succeed.

@chadlwilson

Copy link
Copy Markdown
Contributor

Thanks for the tips!

I noted something similar about the "appears to succeed" in jruby/jruby#8886 which is a related issue (the one I was trying to workaround with JARS_SKIP in the first place since I don't actually need psych, I just get it as a transitive). I imagine my setup is sufficiently different that my problems might be something different though.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@kares@headius@donoghuc@chadlwilson
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

bump snakeyaml-engine to 2.10 (jruby) - #762

Merged
headius merged 1 commit into
ruby:masterfrom
kares:bump-snakeyaml-2.10
Dec 11, 2025
Merged

bump snakeyaml-engine to 2.10 (jruby)#762
headius merged 1 commit into
ruby:masterfrom
kares:bump-snakeyaml-2.10

Conversation

@kares

Copy link
Copy Markdown
Contributor

No description provided.

@headius
headius merged commit 5af4cec into ruby:masterDec 11, 2025
75 checks passed
@headius

Copy link
Copy Markdown
Contributor

Thanks @kares!

donoghuc added a commit to donoghuc/logstash that referenced this pull request 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.
@donoghuc

Copy link
Copy Markdown

@kares@headius Would we expect that the snakeyaml-engine for psych need to match the version vendored with jruby? For example when running psych 5.3.1 with jruby 9.4.13.0 (which ships with snakeyaml-engine 2.9) we are seeing issues with bundler (see elastic/logstash#18507 (comment))

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'

Seems related to the maven/jar-dependencies rabbit hole this points to #690

donoghuc added a commit to elastic/logstash that referenced this pull request 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.
mergifyBot pushed a commit to elastic/logstash that referenced this pull request 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.
(cherry picked from commit a089904)
mashhurs pushed a commit to elastic/logstash that referenced this pull request 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.
(cherry picked from commit a089904)
Co-authored-by: Cas Donoghue <cas.donoghue@gmail.com>
@kares

Copy link
Copy Markdown
ContributorAuthor

for the embedded use-case, Logstah is, this really is up to you to manage.

you can e.g. take on jar-deps to be better aligned with your use-case, unless the plan is to comment on every jar dependency bump on external gems.

@donoghuc

Copy link
Copy Markdown

It seems like with jruby 9.4.13.0 and bundler 2.6.3 at least, the issue is independent of logstash. For example:

For this Gemfile:

source "https://rubygems.org"
gem 'psych', '~> 5.3.1'

A bundle install gives this error:

Fetching gem metadata from https://rubygems.org/........
Resolving dependencies...
Fetching date 3.5.1 (java)
Installing date 3.5.1 (java)
Fetching psych 5.3.1 (java)
Installing psych 5.3.1 (java)
jar dependencies for psych-5.3.1-java.gemspec . . .
org.snakeyaml:snakeyaml-engine:2.10:compile
[ERROR] Failed to execute goal on project jars: Could not collect dependencies for project no_group_id_given:jars:jar:0.0.0
[ERROR] Failed to read artifact descriptor for org.snakeyaml:snakeyaml-engine:jar:2.10
[ERROR] Caused by: The following artifacts could not be resolved: org.snakeyaml:snakeyaml-engine:pom:2.10 (absent): Could not transfer artifact org.snakeyaml:snakeyaml-engine:pom:2.10 from/to central (https://repo.maven.apache.org/maven2): Operation timed out
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
--- ERROR REPORT TEMPLATE -------------------------------------------------------

Errno::ENOENT: No such file or directory - /Users/cas/.rbenv/versions/jruby-9.4.13.0/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/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:76:in load_from_maven' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:221:in install_dependencies'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:210:in do_install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:155:in vendor_jars'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/defaults/jruby.rb:110:in block in <main>' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/installer.rb:367:in block in run_post_install_hooks'
org/jruby/RubyArray.java:2009:in each' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/installer.rb:366:in run_post_install_hooks'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/rubygems_gem_installer.rb:48:in install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/source/rubygems.rb:205:in install'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/gem_installer.rb:55:in install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/gem_installer.rb:17:in install_from_spec'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/parallel_installer.rb:133:in do_install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/parallel_installer.rb:124:in block in worker_pool'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:62:in apply_func' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:57:in block in process_queue'
org/jruby/RubyKernel.java:1725:in loop' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:54:in process_queue'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:90:in `block in create_threads'


## Environment

Bundler 2.6.3
Platforms ruby, universal-java-21
Ruby 3.1.4p0 (2025-06-10 revision 9938a3461fbfdf6048dda0a0411551d6a433581a) [universal-java-21]
Full Path /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin/jruby
Config Dir /Users/cas/.rbenv/versions/jruby-9.4.13.0/etc
RubyGems 3.6.3
Gem Home /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared
Gem Path /Users/cas/.local/share/gem/jruby/3.1.0:/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared
User Home /Users/cas
User Path /Users/cas/.local/share/gem/jruby/3.1.0
Bin Dir /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin
OpenSSL
Compiled JRuby-OpenSSL 0.15.4
Loaded JRuby-OpenSSL 0.15.4
Cert File /opt/homebrew/Cellar/openjdk@21/21.0.6/libexec/openjdk.jdk/Contents/Home/lib/security/cacerts
Cert Dir /etc/ssl/certs
Tools
Git 2.47.0
RVM not installed
rbenv rbenv 1.3.2
chruby not installed
Gem.ruby /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin/jruby
bundle #! /usr/bin/env jruby


## Bundler Build Metadata

Built At 2025-01-16
Git SHA 3c7c4ff2d8f
Released Version true


## Gemfile
### Gemfile
```ruby
source "https://rubygems.org"
gem 'psych', '~> 5.3.1'

Gemfile.lock

<No /private/tmp/bar/Gemfile.lock found>

--- TEMPLATE END ----------------------------------------------------------------

Unfortunately, an unexpected error occurred, and Bundler cannot continue.

First, try this link to see if there are any existing issue reports for this error:
https://github.com/rubygems/rubygems/search?q=No+such+file+or+directory+-+%2FUsers%2Fcas%2F.rbenv%2Fversions%2Fjruby-9.4.13.0%2Flib%2Fruby%2Fgems%2Fshared%2Fgems%2Fpsych-5.3.1-java%2Fdeps.lst&type=Issues

If there aren't any reports for this error yet, please fill in the new issue form located at https://github.com/rubygems/rubygems/issues/new?labels=Bundler&template=bundler-related-issue.md, and copy and paste the report template above in there.

@donoghuc

Copy link
Copy Markdown

Actually disregard that! Sorry, I had a local maven config that was using a broken proxy 🤦 Jar-dependencies is able to manage the snakeyaml-engine jar.

@chadlwilson

chadlwilson commented Dec 19, 2025

Copy link
Copy Markdown
Contributor

Yeah, this broke gocd too with the a similar error; except a file not found on the jar. I suspect there could be a bug in jar_dependencies, possibly when using an existing cached jar_dependencies alongside BUNDLE_GLOBAL_GEM_CACHE and JARS_SKIP in my case.

@donoghuc - did you have to do anything in particular with your proxy to "unbreak" it, in case my issue is that too?

@donoghuc

Copy link
Copy Markdown

@chadlwilson i found that setting the JARS_DEBUG=true and JARS_VERBOSE=true environment variables when doing the install helped explain exactly what the issue was. In my case i had a defunct proxy configured in my ~/.m2/settings.xml file.

One note that i found frustrating was that in the case I mentioned in this comment #762 (comment) the rest of the psych gem would install (just not the snakeyaml-engine jar) and then subsequent bundle installs would appear to succeed.

@chadlwilson

Copy link
Copy Markdown
Contributor

Thanks for the tips!

I noted something similar about the "appears to succeed" in jruby/jruby#8886 which is a related issue (the one I was trying to workaround with JARS_SKIP in the first place since I don't actually need psych, I just get it as a transitive). I imagine my setup is sufficiently different that my problems might be something different though.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@kares@headius@donoghuc@chadlwilson
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

bump snakeyaml-engine to 2.10 (jruby) - #762

Merged
headius merged 1 commit into
ruby:masterfrom
kares:bump-snakeyaml-2.10
Dec 11, 2025
Merged

bump snakeyaml-engine to 2.10 (jruby)#762
headius merged 1 commit into
ruby:masterfrom
kares:bump-snakeyaml-2.10

Conversation

@kares

Copy link
Copy Markdown
Contributor

No description provided.

@headius
headius merged commit 5af4cec into ruby:masterDec 11, 2025
75 checks passed
@headius

Copy link
Copy Markdown
Contributor

Thanks @kares!

donoghuc added a commit to donoghuc/logstash that referenced this pull request 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.
@donoghuc

Copy link
Copy Markdown

@kares@headius Would we expect that the snakeyaml-engine for psych need to match the version vendored with jruby? For example when running psych 5.3.1 with jruby 9.4.13.0 (which ships with snakeyaml-engine 2.9) we are seeing issues with bundler (see elastic/logstash#18507 (comment))

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'

Seems related to the maven/jar-dependencies rabbit hole this points to #690

donoghuc added a commit to elastic/logstash that referenced this pull request 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.
mergifyBot pushed a commit to elastic/logstash that referenced this pull request 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.
(cherry picked from commit a089904)
mashhurs pushed a commit to elastic/logstash that referenced this pull request 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.
(cherry picked from commit a089904)
Co-authored-by: Cas Donoghue <cas.donoghue@gmail.com>
@kares

Copy link
Copy Markdown
ContributorAuthor

for the embedded use-case, Logstah is, this really is up to you to manage.

you can e.g. take on jar-deps to be better aligned with your use-case, unless the plan is to comment on every jar dependency bump on external gems.

@donoghuc

Copy link
Copy Markdown

It seems like with jruby 9.4.13.0 and bundler 2.6.3 at least, the issue is independent of logstash. For example:

For this Gemfile:

source "https://rubygems.org"
gem 'psych', '~> 5.3.1'

A bundle install gives this error:

Fetching gem metadata from https://rubygems.org/........
Resolving dependencies...
Fetching date 3.5.1 (java)
Installing date 3.5.1 (java)
Fetching psych 5.3.1 (java)
Installing psych 5.3.1 (java)
jar dependencies for psych-5.3.1-java.gemspec . . .
org.snakeyaml:snakeyaml-engine:2.10:compile
[ERROR] Failed to execute goal on project jars: Could not collect dependencies for project no_group_id_given:jars:jar:0.0.0
[ERROR] Failed to read artifact descriptor for org.snakeyaml:snakeyaml-engine:jar:2.10
[ERROR] Caused by: The following artifacts could not be resolved: org.snakeyaml:snakeyaml-engine:pom:2.10 (absent): Could not transfer artifact org.snakeyaml:snakeyaml-engine:pom:2.10 from/to central (https://repo.maven.apache.org/maven2): Operation timed out
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
--- ERROR REPORT TEMPLATE -------------------------------------------------------

Errno::ENOENT: No such file or directory - /Users/cas/.rbenv/versions/jruby-9.4.13.0/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/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:76:in load_from_maven' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:221:in install_dependencies'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:210:in do_install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:155:in vendor_jars'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/defaults/jruby.rb:110:in block in <main>' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/installer.rb:367:in block in run_post_install_hooks'
org/jruby/RubyArray.java:2009:in each' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/installer.rb:366:in run_post_install_hooks'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/rubygems_gem_installer.rb:48:in install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/source/rubygems.rb:205:in install'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/gem_installer.rb:55:in install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/gem_installer.rb:17:in install_from_spec'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/parallel_installer.rb:133:in do_install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/parallel_installer.rb:124:in block in worker_pool'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:62:in apply_func' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:57:in block in process_queue'
org/jruby/RubyKernel.java:1725:in loop' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:54:in process_queue'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:90:in `block in create_threads'


## Environment

Bundler 2.6.3
Platforms ruby, universal-java-21
Ruby 3.1.4p0 (2025-06-10 revision 9938a3461fbfdf6048dda0a0411551d6a433581a) [universal-java-21]
Full Path /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin/jruby
Config Dir /Users/cas/.rbenv/versions/jruby-9.4.13.0/etc
RubyGems 3.6.3
Gem Home /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared
Gem Path /Users/cas/.local/share/gem/jruby/3.1.0:/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared
User Home /Users/cas
User Path /Users/cas/.local/share/gem/jruby/3.1.0
Bin Dir /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin
OpenSSL
Compiled JRuby-OpenSSL 0.15.4
Loaded JRuby-OpenSSL 0.15.4
Cert File /opt/homebrew/Cellar/openjdk@21/21.0.6/libexec/openjdk.jdk/Contents/Home/lib/security/cacerts
Cert Dir /etc/ssl/certs
Tools
Git 2.47.0
RVM not installed
rbenv rbenv 1.3.2
chruby not installed
Gem.ruby /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin/jruby
bundle #! /usr/bin/env jruby


## Bundler Build Metadata

Built At 2025-01-16
Git SHA 3c7c4ff2d8f
Released Version true


## Gemfile
### Gemfile
```ruby
source "https://rubygems.org"
gem 'psych', '~> 5.3.1'

Gemfile.lock

<No /private/tmp/bar/Gemfile.lock found>

--- TEMPLATE END ----------------------------------------------------------------

Unfortunately, an unexpected error occurred, and Bundler cannot continue.

First, try this link to see if there are any existing issue reports for this error:
https://github.com/rubygems/rubygems/search?q=No+such+file+or+directory+-+%2FUsers%2Fcas%2F.rbenv%2Fversions%2Fjruby-9.4.13.0%2Flib%2Fruby%2Fgems%2Fshared%2Fgems%2Fpsych-5.3.1-java%2Fdeps.lst&type=Issues

If there aren't any reports for this error yet, please fill in the new issue form located at https://github.com/rubygems/rubygems/issues/new?labels=Bundler&template=bundler-related-issue.md, and copy and paste the report template above in there.

@donoghuc

Copy link
Copy Markdown

Actually disregard that! Sorry, I had a local maven config that was using a broken proxy 🤦 Jar-dependencies is able to manage the snakeyaml-engine jar.

@chadlwilson

chadlwilson commented Dec 19, 2025

Copy link
Copy Markdown
Contributor

Yeah, this broke gocd too with the a similar error; except a file not found on the jar. I suspect there could be a bug in jar_dependencies, possibly when using an existing cached jar_dependencies alongside BUNDLE_GLOBAL_GEM_CACHE and JARS_SKIP in my case.

@donoghuc - did you have to do anything in particular with your proxy to "unbreak" it, in case my issue is that too?

@donoghuc

Copy link
Copy Markdown

@chadlwilson i found that setting the JARS_DEBUG=true and JARS_VERBOSE=true environment variables when doing the install helped explain exactly what the issue was. In my case i had a defunct proxy configured in my ~/.m2/settings.xml file.

One note that i found frustrating was that in the case I mentioned in this comment #762 (comment) the rest of the psych gem would install (just not the snakeyaml-engine jar) and then subsequent bundle installs would appear to succeed.

@chadlwilson

Copy link
Copy Markdown
Contributor

Thanks for the tips!

I noted something similar about the "appears to succeed" in jruby/jruby#8886 which is a related issue (the one I was trying to workaround with JARS_SKIP in the first place since I don't actually need psych, I just get it as a transitive). I imagine my setup is sufficiently different that my problems might be something different though.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@kares@headius@donoghuc@chadlwilson
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

bump snakeyaml-engine to 2.10 (jruby) - #762

Merged
headius merged 1 commit into
ruby:masterfrom
kares:bump-snakeyaml-2.10
Dec 11, 2025
Merged

bump snakeyaml-engine to 2.10 (jruby)#762
headius merged 1 commit into
ruby:masterfrom
kares:bump-snakeyaml-2.10

Conversation

@kares

Copy link
Copy Markdown
Contributor

No description provided.

@headius
headius merged commit 5af4cec into ruby:masterDec 11, 2025
75 checks passed
@headius

Copy link
Copy Markdown
Contributor

Thanks @kares!

donoghuc added a commit to donoghuc/logstash that referenced this pull request 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.
@donoghuc

Copy link
Copy Markdown

@kares@headius Would we expect that the snakeyaml-engine for psych need to match the version vendored with jruby? For example when running psych 5.3.1 with jruby 9.4.13.0 (which ships with snakeyaml-engine 2.9) we are seeing issues with bundler (see elastic/logstash#18507 (comment))

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'

Seems related to the maven/jar-dependencies rabbit hole this points to #690

donoghuc added a commit to elastic/logstash that referenced this pull request 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.
mergifyBot pushed a commit to elastic/logstash that referenced this pull request 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.
(cherry picked from commit a089904)
mashhurs pushed a commit to elastic/logstash that referenced this pull request 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.
(cherry picked from commit a089904)
Co-authored-by: Cas Donoghue <cas.donoghue@gmail.com>
@kares

Copy link
Copy Markdown
ContributorAuthor

for the embedded use-case, Logstah is, this really is up to you to manage.

you can e.g. take on jar-deps to be better aligned with your use-case, unless the plan is to comment on every jar dependency bump on external gems.

@donoghuc

Copy link
Copy Markdown

It seems like with jruby 9.4.13.0 and bundler 2.6.3 at least, the issue is independent of logstash. For example:

For this Gemfile:

source "https://rubygems.org"
gem 'psych', '~> 5.3.1'

A bundle install gives this error:

Fetching gem metadata from https://rubygems.org/........
Resolving dependencies...
Fetching date 3.5.1 (java)
Installing date 3.5.1 (java)
Fetching psych 5.3.1 (java)
Installing psych 5.3.1 (java)
jar dependencies for psych-5.3.1-java.gemspec . . .
org.snakeyaml:snakeyaml-engine:2.10:compile
[ERROR] Failed to execute goal on project jars: Could not collect dependencies for project no_group_id_given:jars:jar:0.0.0
[ERROR] Failed to read artifact descriptor for org.snakeyaml:snakeyaml-engine:jar:2.10
[ERROR] Caused by: The following artifacts could not be resolved: org.snakeyaml:snakeyaml-engine:pom:2.10 (absent): Could not transfer artifact org.snakeyaml:snakeyaml-engine:pom:2.10 from/to central (https://repo.maven.apache.org/maven2): Operation timed out
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
--- ERROR REPORT TEMPLATE -------------------------------------------------------

Errno::ENOENT: No such file or directory - /Users/cas/.rbenv/versions/jruby-9.4.13.0/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/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:76:in load_from_maven' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:221:in install_dependencies'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:210:in do_install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:155:in vendor_jars'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/defaults/jruby.rb:110:in block in <main>' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/installer.rb:367:in block in run_post_install_hooks'
org/jruby/RubyArray.java:2009:in each' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/installer.rb:366:in run_post_install_hooks'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/rubygems_gem_installer.rb:48:in install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/source/rubygems.rb:205:in install'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/gem_installer.rb:55:in install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/gem_installer.rb:17:in install_from_spec'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/parallel_installer.rb:133:in do_install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/parallel_installer.rb:124:in block in worker_pool'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:62:in apply_func' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:57:in block in process_queue'
org/jruby/RubyKernel.java:1725:in loop' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:54:in process_queue'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:90:in `block in create_threads'


## Environment

Bundler 2.6.3
Platforms ruby, universal-java-21
Ruby 3.1.4p0 (2025-06-10 revision 9938a3461fbfdf6048dda0a0411551d6a433581a) [universal-java-21]
Full Path /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin/jruby
Config Dir /Users/cas/.rbenv/versions/jruby-9.4.13.0/etc
RubyGems 3.6.3
Gem Home /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared
Gem Path /Users/cas/.local/share/gem/jruby/3.1.0:/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared
User Home /Users/cas
User Path /Users/cas/.local/share/gem/jruby/3.1.0
Bin Dir /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin
OpenSSL
Compiled JRuby-OpenSSL 0.15.4
Loaded JRuby-OpenSSL 0.15.4
Cert File /opt/homebrew/Cellar/openjdk@21/21.0.6/libexec/openjdk.jdk/Contents/Home/lib/security/cacerts
Cert Dir /etc/ssl/certs
Tools
Git 2.47.0
RVM not installed
rbenv rbenv 1.3.2
chruby not installed
Gem.ruby /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin/jruby
bundle #! /usr/bin/env jruby


## Bundler Build Metadata

Built At 2025-01-16
Git SHA 3c7c4ff2d8f
Released Version true


## Gemfile
### Gemfile
```ruby
source "https://rubygems.org"
gem 'psych', '~> 5.3.1'

Gemfile.lock

<No /private/tmp/bar/Gemfile.lock found>

--- TEMPLATE END ----------------------------------------------------------------

Unfortunately, an unexpected error occurred, and Bundler cannot continue.

First, try this link to see if there are any existing issue reports for this error:
https://github.com/rubygems/rubygems/search?q=No+such+file+or+directory+-+%2FUsers%2Fcas%2F.rbenv%2Fversions%2Fjruby-9.4.13.0%2Flib%2Fruby%2Fgems%2Fshared%2Fgems%2Fpsych-5.3.1-java%2Fdeps.lst&type=Issues

If there aren't any reports for this error yet, please fill in the new issue form located at https://github.com/rubygems/rubygems/issues/new?labels=Bundler&template=bundler-related-issue.md, and copy and paste the report template above in there.

@donoghuc

Copy link
Copy Markdown

Actually disregard that! Sorry, I had a local maven config that was using a broken proxy 🤦 Jar-dependencies is able to manage the snakeyaml-engine jar.

@chadlwilson

chadlwilson commented Dec 19, 2025

Copy link
Copy Markdown
Contributor

Yeah, this broke gocd too with the a similar error; except a file not found on the jar. I suspect there could be a bug in jar_dependencies, possibly when using an existing cached jar_dependencies alongside BUNDLE_GLOBAL_GEM_CACHE and JARS_SKIP in my case.

@donoghuc - did you have to do anything in particular with your proxy to "unbreak" it, in case my issue is that too?

@donoghuc

Copy link
Copy Markdown

@chadlwilson i found that setting the JARS_DEBUG=true and JARS_VERBOSE=true environment variables when doing the install helped explain exactly what the issue was. In my case i had a defunct proxy configured in my ~/.m2/settings.xml file.

One note that i found frustrating was that in the case I mentioned in this comment #762 (comment) the rest of the psych gem would install (just not the snakeyaml-engine jar) and then subsequent bundle installs would appear to succeed.

@chadlwilson

Copy link
Copy Markdown
Contributor

Thanks for the tips!

I noted something similar about the "appears to succeed" in jruby/jruby#8886 which is a related issue (the one I was trying to workaround with JARS_SKIP in the first place since I don't actually need psych, I just get it as a transitive). I imagine my setup is sufficiently different that my problems might be something different though.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@kares@headius@donoghuc@chadlwilson
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

bump snakeyaml-engine to 2.10 (jruby) - #762

Merged
headius merged 1 commit into
ruby:masterfrom
kares:bump-snakeyaml-2.10
Dec 11, 2025
Merged

bump snakeyaml-engine to 2.10 (jruby)#762
headius merged 1 commit into
ruby:masterfrom
kares:bump-snakeyaml-2.10

Conversation

@kares

Copy link
Copy Markdown
Contributor

No description provided.

@headius
headius merged commit 5af4cec into ruby:masterDec 11, 2025
75 checks passed
@headius

Copy link
Copy Markdown
Contributor

Thanks @kares!

donoghuc added a commit to donoghuc/logstash that referenced this pull request 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.
@donoghuc

Copy link
Copy Markdown

@kares@headius Would we expect that the snakeyaml-engine for psych need to match the version vendored with jruby? For example when running psych 5.3.1 with jruby 9.4.13.0 (which ships with snakeyaml-engine 2.9) we are seeing issues with bundler (see elastic/logstash#18507 (comment))

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'

Seems related to the maven/jar-dependencies rabbit hole this points to #690

donoghuc added a commit to elastic/logstash that referenced this pull request 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.
mergifyBot pushed a commit to elastic/logstash that referenced this pull request 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.
(cherry picked from commit a089904)
mashhurs pushed a commit to elastic/logstash that referenced this pull request 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.
(cherry picked from commit a089904)
Co-authored-by: Cas Donoghue <cas.donoghue@gmail.com>
@kares

Copy link
Copy Markdown
ContributorAuthor

for the embedded use-case, Logstah is, this really is up to you to manage.

you can e.g. take on jar-deps to be better aligned with your use-case, unless the plan is to comment on every jar dependency bump on external gems.

@donoghuc

Copy link
Copy Markdown

It seems like with jruby 9.4.13.0 and bundler 2.6.3 at least, the issue is independent of logstash. For example:

For this Gemfile:

source "https://rubygems.org"
gem 'psych', '~> 5.3.1'

A bundle install gives this error:

Fetching gem metadata from https://rubygems.org/........
Resolving dependencies...
Fetching date 3.5.1 (java)
Installing date 3.5.1 (java)
Fetching psych 5.3.1 (java)
Installing psych 5.3.1 (java)
jar dependencies for psych-5.3.1-java.gemspec . . .
org.snakeyaml:snakeyaml-engine:2.10:compile
[ERROR] Failed to execute goal on project jars: Could not collect dependencies for project no_group_id_given:jars:jar:0.0.0
[ERROR] Failed to read artifact descriptor for org.snakeyaml:snakeyaml-engine:jar:2.10
[ERROR] Caused by: The following artifacts could not be resolved: org.snakeyaml:snakeyaml-engine:pom:2.10 (absent): Could not transfer artifact org.snakeyaml:snakeyaml-engine:pom:2.10 from/to central (https://repo.maven.apache.org/maven2): Operation timed out
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
--- ERROR REPORT TEMPLATE -------------------------------------------------------

Errno::ENOENT: No such file or directory - /Users/cas/.rbenv/versions/jruby-9.4.13.0/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/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:76:in load_from_maven' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:221:in install_dependencies'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:210:in do_install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:155:in vendor_jars'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/defaults/jruby.rb:110:in block in <main>' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/installer.rb:367:in block in run_post_install_hooks'
org/jruby/RubyArray.java:2009:in each' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/installer.rb:366:in run_post_install_hooks'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/rubygems_gem_installer.rb:48:in install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/source/rubygems.rb:205:in install'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/gem_installer.rb:55:in install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/gem_installer.rb:17:in install_from_spec'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/parallel_installer.rb:133:in do_install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/parallel_installer.rb:124:in block in worker_pool'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:62:in apply_func' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:57:in block in process_queue'
org/jruby/RubyKernel.java:1725:in loop' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:54:in process_queue'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:90:in `block in create_threads'


## Environment

Bundler 2.6.3
Platforms ruby, universal-java-21
Ruby 3.1.4p0 (2025-06-10 revision 9938a3461fbfdf6048dda0a0411551d6a433581a) [universal-java-21]
Full Path /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin/jruby
Config Dir /Users/cas/.rbenv/versions/jruby-9.4.13.0/etc
RubyGems 3.6.3
Gem Home /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared
Gem Path /Users/cas/.local/share/gem/jruby/3.1.0:/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared
User Home /Users/cas
User Path /Users/cas/.local/share/gem/jruby/3.1.0
Bin Dir /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin
OpenSSL
Compiled JRuby-OpenSSL 0.15.4
Loaded JRuby-OpenSSL 0.15.4
Cert File /opt/homebrew/Cellar/openjdk@21/21.0.6/libexec/openjdk.jdk/Contents/Home/lib/security/cacerts
Cert Dir /etc/ssl/certs
Tools
Git 2.47.0
RVM not installed
rbenv rbenv 1.3.2
chruby not installed
Gem.ruby /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin/jruby
bundle #! /usr/bin/env jruby


## Bundler Build Metadata

Built At 2025-01-16
Git SHA 3c7c4ff2d8f
Released Version true


## Gemfile
### Gemfile
```ruby
source "https://rubygems.org"
gem 'psych', '~> 5.3.1'

Gemfile.lock

<No /private/tmp/bar/Gemfile.lock found>

--- TEMPLATE END ----------------------------------------------------------------

Unfortunately, an unexpected error occurred, and Bundler cannot continue.

First, try this link to see if there are any existing issue reports for this error:
https://github.com/rubygems/rubygems/search?q=No+such+file+or+directory+-+%2FUsers%2Fcas%2F.rbenv%2Fversions%2Fjruby-9.4.13.0%2Flib%2Fruby%2Fgems%2Fshared%2Fgems%2Fpsych-5.3.1-java%2Fdeps.lst&type=Issues

If there aren't any reports for this error yet, please fill in the new issue form located at https://github.com/rubygems/rubygems/issues/new?labels=Bundler&template=bundler-related-issue.md, and copy and paste the report template above in there.

@donoghuc

Copy link
Copy Markdown

Actually disregard that! Sorry, I had a local maven config that was using a broken proxy 🤦 Jar-dependencies is able to manage the snakeyaml-engine jar.

@chadlwilson

chadlwilson commented Dec 19, 2025

Copy link
Copy Markdown
Contributor

Yeah, this broke gocd too with the a similar error; except a file not found on the jar. I suspect there could be a bug in jar_dependencies, possibly when using an existing cached jar_dependencies alongside BUNDLE_GLOBAL_GEM_CACHE and JARS_SKIP in my case.

@donoghuc - did you have to do anything in particular with your proxy to "unbreak" it, in case my issue is that too?

@donoghuc

Copy link
Copy Markdown

@chadlwilson i found that setting the JARS_DEBUG=true and JARS_VERBOSE=true environment variables when doing the install helped explain exactly what the issue was. In my case i had a defunct proxy configured in my ~/.m2/settings.xml file.

One note that i found frustrating was that in the case I mentioned in this comment #762 (comment) the rest of the psych gem would install (just not the snakeyaml-engine jar) and then subsequent bundle installs would appear to succeed.

@chadlwilson

Copy link
Copy Markdown
Contributor

Thanks for the tips!

I noted something similar about the "appears to succeed" in jruby/jruby#8886 which is a related issue (the one I was trying to workaround with JARS_SKIP in the first place since I don't actually need psych, I just get it as a transitive). I imagine my setup is sufficiently different that my problems might be something different though.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@kares@headius@donoghuc@chadlwilson
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

bump snakeyaml-engine to 2.10 (jruby) - #762

Merged
headius merged 1 commit into
ruby:masterfrom
kares:bump-snakeyaml-2.10
Dec 11, 2025
Merged

bump snakeyaml-engine to 2.10 (jruby)#762
headius merged 1 commit into
ruby:masterfrom
kares:bump-snakeyaml-2.10

Conversation

@kares

Copy link
Copy Markdown
Contributor

No description provided.

@headius
headius merged commit 5af4cec into ruby:masterDec 11, 2025
75 checks passed
@headius

Copy link
Copy Markdown
Contributor

Thanks @kares!

donoghuc added a commit to donoghuc/logstash that referenced this pull request 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.
@donoghuc

Copy link
Copy Markdown

@kares@headius Would we expect that the snakeyaml-engine for psych need to match the version vendored with jruby? For example when running psych 5.3.1 with jruby 9.4.13.0 (which ships with snakeyaml-engine 2.9) we are seeing issues with bundler (see elastic/logstash#18507 (comment))

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'

Seems related to the maven/jar-dependencies rabbit hole this points to #690

donoghuc added a commit to elastic/logstash that referenced this pull request 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.
mergifyBot pushed a commit to elastic/logstash that referenced this pull request 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.
(cherry picked from commit a089904)
mashhurs pushed a commit to elastic/logstash that referenced this pull request 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.
(cherry picked from commit a089904)
Co-authored-by: Cas Donoghue <cas.donoghue@gmail.com>
@kares

Copy link
Copy Markdown
ContributorAuthor

for the embedded use-case, Logstah is, this really is up to you to manage.

you can e.g. take on jar-deps to be better aligned with your use-case, unless the plan is to comment on every jar dependency bump on external gems.

@donoghuc

Copy link
Copy Markdown

It seems like with jruby 9.4.13.0 and bundler 2.6.3 at least, the issue is independent of logstash. For example:

For this Gemfile:

source "https://rubygems.org"
gem 'psych', '~> 5.3.1'

A bundle install gives this error:

Fetching gem metadata from https://rubygems.org/........
Resolving dependencies...
Fetching date 3.5.1 (java)
Installing date 3.5.1 (java)
Fetching psych 5.3.1 (java)
Installing psych 5.3.1 (java)
jar dependencies for psych-5.3.1-java.gemspec . . .
org.snakeyaml:snakeyaml-engine:2.10:compile
[ERROR] Failed to execute goal on project jars: Could not collect dependencies for project no_group_id_given:jars:jar:0.0.0
[ERROR] Failed to read artifact descriptor for org.snakeyaml:snakeyaml-engine:jar:2.10
[ERROR] Caused by: The following artifacts could not be resolved: org.snakeyaml:snakeyaml-engine:pom:2.10 (absent): Could not transfer artifact org.snakeyaml:snakeyaml-engine:pom:2.10 from/to central (https://repo.maven.apache.org/maven2): Operation timed out
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
--- ERROR REPORT TEMPLATE -------------------------------------------------------

Errno::ENOENT: No such file or directory - /Users/cas/.rbenv/versions/jruby-9.4.13.0/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/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:76:in load_from_maven' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:221:in install_dependencies'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:210:in do_install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:155:in vendor_jars'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/defaults/jruby.rb:110:in block in <main>' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/installer.rb:367:in block in run_post_install_hooks'
org/jruby/RubyArray.java:2009:in each' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/installer.rb:366:in run_post_install_hooks'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/rubygems_gem_installer.rb:48:in install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/source/rubygems.rb:205:in install'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/gem_installer.rb:55:in install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/gem_installer.rb:17:in install_from_spec'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/parallel_installer.rb:133:in do_install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/parallel_installer.rb:124:in block in worker_pool'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:62:in apply_func' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:57:in block in process_queue'
org/jruby/RubyKernel.java:1725:in loop' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:54:in process_queue'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:90:in `block in create_threads'


## Environment

Bundler 2.6.3
Platforms ruby, universal-java-21
Ruby 3.1.4p0 (2025-06-10 revision 9938a3461fbfdf6048dda0a0411551d6a433581a) [universal-java-21]
Full Path /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin/jruby
Config Dir /Users/cas/.rbenv/versions/jruby-9.4.13.0/etc
RubyGems 3.6.3
Gem Home /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared
Gem Path /Users/cas/.local/share/gem/jruby/3.1.0:/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared
User Home /Users/cas
User Path /Users/cas/.local/share/gem/jruby/3.1.0
Bin Dir /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin
OpenSSL
Compiled JRuby-OpenSSL 0.15.4
Loaded JRuby-OpenSSL 0.15.4
Cert File /opt/homebrew/Cellar/openjdk@21/21.0.6/libexec/openjdk.jdk/Contents/Home/lib/security/cacerts
Cert Dir /etc/ssl/certs
Tools
Git 2.47.0
RVM not installed
rbenv rbenv 1.3.2
chruby not installed
Gem.ruby /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin/jruby
bundle #! /usr/bin/env jruby


## Bundler Build Metadata

Built At 2025-01-16
Git SHA 3c7c4ff2d8f
Released Version true


## Gemfile
### Gemfile
```ruby
source "https://rubygems.org"
gem 'psych', '~> 5.3.1'

Gemfile.lock

<No /private/tmp/bar/Gemfile.lock found>

--- TEMPLATE END ----------------------------------------------------------------

Unfortunately, an unexpected error occurred, and Bundler cannot continue.

First, try this link to see if there are any existing issue reports for this error:
https://github.com/rubygems/rubygems/search?q=No+such+file+or+directory+-+%2FUsers%2Fcas%2F.rbenv%2Fversions%2Fjruby-9.4.13.0%2Flib%2Fruby%2Fgems%2Fshared%2Fgems%2Fpsych-5.3.1-java%2Fdeps.lst&type=Issues

If there aren't any reports for this error yet, please fill in the new issue form located at https://github.com/rubygems/rubygems/issues/new?labels=Bundler&template=bundler-related-issue.md, and copy and paste the report template above in there.

@donoghuc

Copy link
Copy Markdown

Actually disregard that! Sorry, I had a local maven config that was using a broken proxy 🤦 Jar-dependencies is able to manage the snakeyaml-engine jar.

@chadlwilson

chadlwilson commented Dec 19, 2025

Copy link
Copy Markdown
Contributor

Yeah, this broke gocd too with the a similar error; except a file not found on the jar. I suspect there could be a bug in jar_dependencies, possibly when using an existing cached jar_dependencies alongside BUNDLE_GLOBAL_GEM_CACHE and JARS_SKIP in my case.

@donoghuc - did you have to do anything in particular with your proxy to "unbreak" it, in case my issue is that too?

@donoghuc

Copy link
Copy Markdown

@chadlwilson i found that setting the JARS_DEBUG=true and JARS_VERBOSE=true environment variables when doing the install helped explain exactly what the issue was. In my case i had a defunct proxy configured in my ~/.m2/settings.xml file.

One note that i found frustrating was that in the case I mentioned in this comment #762 (comment) the rest of the psych gem would install (just not the snakeyaml-engine jar) and then subsequent bundle installs would appear to succeed.

@chadlwilson

Copy link
Copy Markdown
Contributor

Thanks for the tips!

I noted something similar about the "appears to succeed" in jruby/jruby#8886 which is a related issue (the one I was trying to workaround with JARS_SKIP in the first place since I don't actually need psych, I just get it as a transitive). I imagine my setup is sufficiently different that my problems might be something different though.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@kares@headius@donoghuc@chadlwilson
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

bump snakeyaml-engine to 2.10 (jruby) - #762

Merged
headius merged 1 commit into
ruby:masterfrom
kares:bump-snakeyaml-2.10
Dec 11, 2025
Merged

bump snakeyaml-engine to 2.10 (jruby)#762
headius merged 1 commit into
ruby:masterfrom
kares:bump-snakeyaml-2.10

Conversation

@kares

Copy link
Copy Markdown
Contributor

No description provided.

@headius
headius merged commit 5af4cec into ruby:masterDec 11, 2025
75 checks passed
@headius

Copy link
Copy Markdown
Contributor

Thanks @kares!

donoghuc added a commit to donoghuc/logstash that referenced this pull request 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.
@donoghuc

Copy link
Copy Markdown

@kares@headius Would we expect that the snakeyaml-engine for psych need to match the version vendored with jruby? For example when running psych 5.3.1 with jruby 9.4.13.0 (which ships with snakeyaml-engine 2.9) we are seeing issues with bundler (see elastic/logstash#18507 (comment))

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'

Seems related to the maven/jar-dependencies rabbit hole this points to #690

donoghuc added a commit to elastic/logstash that referenced this pull request 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.
mergifyBot pushed a commit to elastic/logstash that referenced this pull request 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.
(cherry picked from commit a089904)
mashhurs pushed a commit to elastic/logstash that referenced this pull request 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.
(cherry picked from commit a089904)
Co-authored-by: Cas Donoghue <cas.donoghue@gmail.com>
@kares

Copy link
Copy Markdown
ContributorAuthor

for the embedded use-case, Logstah is, this really is up to you to manage.

you can e.g. take on jar-deps to be better aligned with your use-case, unless the plan is to comment on every jar dependency bump on external gems.

@donoghuc

Copy link
Copy Markdown

It seems like with jruby 9.4.13.0 and bundler 2.6.3 at least, the issue is independent of logstash. For example:

For this Gemfile:

source "https://rubygems.org"
gem 'psych', '~> 5.3.1'

A bundle install gives this error:

Fetching gem metadata from https://rubygems.org/........
Resolving dependencies...
Fetching date 3.5.1 (java)
Installing date 3.5.1 (java)
Fetching psych 5.3.1 (java)
Installing psych 5.3.1 (java)
jar dependencies for psych-5.3.1-java.gemspec . . .
org.snakeyaml:snakeyaml-engine:2.10:compile
[ERROR] Failed to execute goal on project jars: Could not collect dependencies for project no_group_id_given:jars:jar:0.0.0
[ERROR] Failed to read artifact descriptor for org.snakeyaml:snakeyaml-engine:jar:2.10
[ERROR] Caused by: The following artifacts could not be resolved: org.snakeyaml:snakeyaml-engine:pom:2.10 (absent): Could not transfer artifact org.snakeyaml:snakeyaml-engine:pom:2.10 from/to central (https://repo.maven.apache.org/maven2): Operation timed out
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
--- ERROR REPORT TEMPLATE -------------------------------------------------------

Errno::ENOENT: No such file or directory - /Users/cas/.rbenv/versions/jruby-9.4.13.0/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/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:76:in load_from_maven' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:221:in install_dependencies'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:210:in do_install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared/gems/jar-dependencies-0.5.5/lib/jars/installer.rb:155:in vendor_jars'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/defaults/jruby.rb:110:in block in <main>' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/installer.rb:367:in block in run_post_install_hooks'
org/jruby/RubyArray.java:2009:in each' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/rubygems/installer.rb:366:in run_post_install_hooks'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/rubygems_gem_installer.rb:48:in install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/source/rubygems.rb:205:in install'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/gem_installer.rb:55:in install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/gem_installer.rb:17:in install_from_spec'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/parallel_installer.rb:133:in do_install' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/installer/parallel_installer.rb:124:in block in worker_pool'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:62:in apply_func' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:57:in block in process_queue'
org/jruby/RubyKernel.java:1725:in loop' /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:54:in process_queue'
/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/stdlib/bundler/worker.rb:90:in `block in create_threads'


## Environment

Bundler 2.6.3
Platforms ruby, universal-java-21
Ruby 3.1.4p0 (2025-06-10 revision 9938a3461fbfdf6048dda0a0411551d6a433581a) [universal-java-21]
Full Path /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin/jruby
Config Dir /Users/cas/.rbenv/versions/jruby-9.4.13.0/etc
RubyGems 3.6.3
Gem Home /Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared
Gem Path /Users/cas/.local/share/gem/jruby/3.1.0:/Users/cas/.rbenv/versions/jruby-9.4.13.0/lib/ruby/gems/shared
User Home /Users/cas
User Path /Users/cas/.local/share/gem/jruby/3.1.0
Bin Dir /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin
OpenSSL
Compiled JRuby-OpenSSL 0.15.4
Loaded JRuby-OpenSSL 0.15.4
Cert File /opt/homebrew/Cellar/openjdk@21/21.0.6/libexec/openjdk.jdk/Contents/Home/lib/security/cacerts
Cert Dir /etc/ssl/certs
Tools
Git 2.47.0
RVM not installed
rbenv rbenv 1.3.2
chruby not installed
Gem.ruby /Users/cas/.rbenv/versions/jruby-9.4.13.0/bin/jruby
bundle #! /usr/bin/env jruby


## Bundler Build Metadata

Built At 2025-01-16
Git SHA 3c7c4ff2d8f
Released Version true


## Gemfile
### Gemfile
```ruby
source "https://rubygems.org"
gem 'psych', '~> 5.3.1'

Gemfile.lock

<No /private/tmp/bar/Gemfile.lock found>

--- TEMPLATE END ----------------------------------------------------------------

Unfortunately, an unexpected error occurred, and Bundler cannot continue.

First, try this link to see if there are any existing issue reports for this error:
https://github.com/rubygems/rubygems/search?q=No+such+file+or+directory+-+%2FUsers%2Fcas%2F.rbenv%2Fversions%2Fjruby-9.4.13.0%2Flib%2Fruby%2Fgems%2Fshared%2Fgems%2Fpsych-5.3.1-java%2Fdeps.lst&type=Issues

If there aren't any reports for this error yet, please fill in the new issue form located at https://github.com/rubygems/rubygems/issues/new?labels=Bundler&template=bundler-related-issue.md, and copy and paste the report template above in there.

@donoghuc

Copy link
Copy Markdown

Actually disregard that! Sorry, I had a local maven config that was using a broken proxy 🤦 Jar-dependencies is able to manage the snakeyaml-engine jar.

@chadlwilson

chadlwilson commented Dec 19, 2025

Copy link
Copy Markdown
Contributor

Yeah, this broke gocd too with the a similar error; except a file not found on the jar. I suspect there could be a bug in jar_dependencies, possibly when using an existing cached jar_dependencies alongside BUNDLE_GLOBAL_GEM_CACHE and JARS_SKIP in my case.

@donoghuc - did you have to do anything in particular with your proxy to "unbreak" it, in case my issue is that too?

@donoghuc

Copy link
Copy Markdown

@chadlwilson i found that setting the JARS_DEBUG=true and JARS_VERBOSE=true environment variables when doing the install helped explain exactly what the issue was. In my case i had a defunct proxy configured in my ~/.m2/settings.xml file.

One note that i found frustrating was that in the case I mentioned in this comment #762 (comment) the rest of the psych gem would install (just not the snakeyaml-engine jar) and then subsequent bundle installs would appear to succeed.

@chadlwilson

Copy link
Copy Markdown
Contributor

Thanks for the tips!

I noted something similar about the "appears to succeed" in jruby/jruby#8886 which is a related issue (the one I was trying to workaround with JARS_SKIP in the first place since I don't actually need psych, I just get it as a transitive). I imagine my setup is sufficiently different that my problems might be something different though.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@kares@headius@donoghuc@chadlwilson