-
Notifications
You must be signed in to change notification settings - Fork 212
bump snakeyaml-engine to 2.10 (jruby) #762
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Thanks @kares! |
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.
|
@kares @headius Would we expect that the Seems related to the maven/jar-dependencies rabbit hole this points to #690 |
The latest psych 5.3 minor version has bumped snakeyaml-engine ruby/psych#762. This is causing issues in bundler. Constrain the psych gem to the 5.2 minor version while we are still on jruby 9.4.13.0.
The 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)
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>
|
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. |
|
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: A 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 Bundler 2.6.3 Built At 2025-01-16 Gemfile.lock--- 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: 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. |
|
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. |
|
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 @donoghuc - did you have to do anything in particular with your proxy to "unbreak" it, in case my issue is that too? |
|
@chadlwilson i found that setting the 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. |
|
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. |
No description provided.