Reactor suddenly throws NoMethodError but can't find reason about puma

[MSP-Greg]

The error is in the line shown below, which indicates that the status being returned by your app is nil. The rack spec states that
"It must be an Integer greater than or equal to 100."

It seems the error is in the lowlevel_error_handler you've shown above. It must return a valid response.

puma/lib/puma/request.rb

Line 607 in cdb2341

resp_info[:no_body] ||= status < 200 || STATUS_WITH_NO_ENTITY_BODY[status]

[dentarg]

By the way, if you use a recent enough version of sentry-ruby, it will automatically monkey-patch Puma to capture the low-level errors.

So you don't need to capture the exception yourself in that case.

[dentarg]

Yes, since #3094 (Puma v6.4.0) the result of the lowlevel_error_handler is sent as a response to the client.

By the way, if you use a recent enough version of sentry-ruby, it will automatically monkey-patch Puma to capture the low-level errors.

[taeyeob]

By the way, if you use a recent enough version of sentry-ruby, it will automatically monkey-patch Puma to capture the low-level errors.

So you don't need to capture the exception yourself in that case.

The error is in the line shown below, which indicates that the status being returned by your app is nil. The rack spec states that "It must be an Integer greater than or equal to 100."

It seems the error is in the lowlevel_error_handler you've shown above. It must return a valid response.

puma/lib/puma/request.rb

Line 607 in cdb2341

resp_info[:no_body] ||= status < 200 || STATUS_WITH_NO_ENTITY_BODY[status]

Thanks to all :) It was my only experience to upgrade ruby all the way down from 2.5 to 3.2, so I didn't get a notice on what should I do to prepare for the change.
With your advise, I have commented out the lowlevel_error_handler part and this is my final output:

threads_min_count = ENV.fetch('RAILS_MIN_THREADS') { 0 }
threads_max_count = ENV.fetch('RAILS_MAX_THREADS') { 32 }
env = ENV.fetch('RAILS_ENV') { 'development' }

threads threads_min_count, threads_max_count

port ENV.fetch('PORT') { 3030 }

# development / staging / production
environment env

workers ENV.fetch('WEB_CONCURRENCY') { 1 } unless RUBY_PLATFORM =~ /mingw/

pidfile 'tmp/pids/puma.pid'
state_path 'tmp/pids/puma.state'

# lowlevel_error_handler do |ex, env, status|
#   Sentry.capture_exception(
#     ex,
#     :message => ex.message,
#     :extra => { :puma => env },
#     :transaction => "Puma"
#   )
# end

bind 'unix:///tmp/puma.sock' unless RUBY_PLATFORM =~ /mingw/

prune_bundler

# on_worker_boot do
#   $hackle_client = Hackle.client(sdk_key: ENV['HACKLE_SDK_KEY'])
# end

Just to check for any misunderstandings that might have arisen from my poor English, could you please verify whether itis correct or if I've did the wrong way?

[dentarg]

Yes, exactly, that is the suggestion.

You can also still use lowlevel_error_handler but the last line in it must be a proper response. The README has an example of that: https://github.com/puma/puma#error-handling

[taeyeob]

Okay, I think I got the point.
I will try another if there is any further issues.
Thank you so much 😊😊