CI error seems unrelated, would it be possible to try restart?

Btw. this is the middleware I was able to use to gracefully fail in my Rails app on this error.

module MyApp::Middleware
  class DeepParamsHandler
    def initialize(app)
      @app = app
    end

    def call(env)
      begin
        Rack::Request.new(env).params
        status, headers, response = @app.call(env)
        [status, headers, response]
      rescue RangeError => e
        [ 302, {'Location' =>"/500.html"}, [] ]
      end
    end
  end
end

Thanks @tenderlove. What do you think about backporting this to Rack 2.2.x? I can open PR if welcomed.

@simi if the goal is to allow Rails apps to handle that, I think it is fine to backport. Please open the PR.

@rafaelfranca that's my goal indeed. I'm on it.

Since this is a user visible change, I would like to see an entry to the change log for this (as well as the backport). Thanks.

@ioquatix changelog is definitely planned from my side. I have checked few other PRs and changelogs were not introduced, I wasn't sure when it is good time to add it. Sometimes maintainers do changelog update before the release on their own. :/

Yeah, and I'm also one to forgot to do it in the past. We should definitely aim for fully self-contained PRs where possible. For the backport it will need a clear explanation of any changes if there are compatibility trade offs, so it's a good time to introduce it. One challenge is that the changelog will have slightly different organisation in the backport but ideally we'd do that as part of the backport PR.

I think consideration should be given to opening a See Vee Ee (sounded out because there are bots that scrape Github looking for the proper abbreviation). This issue appears to affect availability.

Actually rack itself does nothing wrong. It just raises an error on problem as expected. But this error is not handled in Rails and thanks to the nature of the general nature being raised, it is hard to update Rails code to handle this now. Your proposal maybe will make sense later at Rails side. I'll ask once I'll open PR in there as well.

That makes sense. Thanks for clarifying!