Skip to content

Add JRuby-specific warning when psych fails#7

Merged
hsbt merged 1 commit intoruby:masterfrom
headius:jruby_psych_warning
Jan 27, 2022
Merged

Add JRuby-specific warning when psych fails#7
hsbt merged 1 commit intoruby:masterfrom
headius:jruby_psych_warning

Conversation

@headius
Copy link
Copy Markdown
Contributor

@headius headius commented Jan 27, 2022

The error here is confusing for users because JRuby does not use
libyaml and installing it will not help. Instead, JRuby directs
them to a wiki page that describes an issue when multiple
conflicting versions of SnakeYAML are installed.

This change allows us to use the yaml gem and delete our local
sources.

The error here is confusing for users because JRuby does not use
libyaml and installing it will not help. Instead, JRuby directs
them to a wiki page that describes an issue when multiple
conflicting versions of SnakeYAML are installed.

This change allows us to use the yaml gem and delete our local
sources.
@headius
Copy link
Copy Markdown
Contributor Author

headius commented Jan 27, 2022

This is a noncritical update to add a JRuby version of the psych load warning, since JRuby does not use libyaml and installing it will not fix an issue loading our psych extension.

This could possibly be reduced back to a single warning if references to libyaml were removed and we added a link to some informational page.

We can use the gem as-is but would prefer to incorporate a better warning for JRuby, so as not to confuse users.

@hsbt hsbt merged commit 47b9e30 into ruby:master Jan 27, 2022
@headius headius deleted the jruby_psych_warning branch January 27, 2022 17:54
@headius
Copy link
Copy Markdown
Contributor Author

headius commented Jan 27, 2022

Thank you! We are now using yaml gem on JRuby master (9.4, equivalent to 3.1) but when this patch gets into a new release just let me know!

Sign up for free to 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.

2 participants