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
2.2.0 regression in JRuby handling of inherited Sinatra::Base keyword args #1749
Comments
dentarg
added a commit
to dentarg/sinatra
that referenced
this issue
Feb 16, 2022
Follows the "The Only Correct Way" from https://eregon.me/blog/2021/02/13/correct-delegation-in-ruby-2-27-3.html Related to sinatra#1670 Fixes sinatra#1749
I answered over on #1750 that it resolves the situation for Logstash. |
jkowens
pushed a commit
that referenced
this issue
Apr 14, 2022
Follows the "The Only Correct Way" from https://eregon.me/blog/2021/02/13/correct-delegation-in-ruby-2-27-3.html Related to #1670 Fixes #1749
jkowens
pushed a commit
that referenced
this issue
Apr 14, 2022
Follows the "The Only Correct Way" from https://eregon.me/blog/2021/02/13/correct-delegation-in-ruby-2-27-3.html Related to #1670 Fixes #1749
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#1670 provides a fix to move forward with Ruby 3.0's Keyword arguments, but it comes at the expense of breaking Sinatra when run under JRuby.
With backtrace
I have filed a separate bug upstream with jruby (jruby/jruby#7102), but am hoping we can find a path foward here in Sinatra while we wait for JRuby to come up with a fix.
The text was updated successfully, but these errors were encountered: