In Rails 7.0.0-alpha2, mobility and good_job seem to conflict using development puma web concurrency

[leehericks]

Context

Standard Rails new using Rails 7.0.0-alpha2 and Ruby 3.0.3 (same issue with 3.0.2)
Local Postgresql 12 database

Run rails new testapp -d postgresql

Edit puma.rb, uncomment (enable) web concurrency and preload_app! (cluster mode)

Add and configure either of mobility or good_job separately and no problem. But together is a problem.
good_job setup

Run rails server

Expected Behavior

Be able to open 127.0.0.1:3000 in your web browser

Actual Behavior

Browser hangs, request doesn't come through on the terminal.

Workaround

Disable web concurrency and run Puma in single mode and then requests run properly. But of course this all works with Puma web concurrency in Rails 6.1.4.1, not sure what changed in Rails 7.0.0-alpha2

[shioyama]

Thanks @leehericks ! I have no idea what might be causing this, I've never heard of anything like this. I'll try to have a look at that repo.

[shioyama]

Ok, I've narrowed down the problem to this file

lib/rails/generators/mobility/backend_generators/base.rb
https://github.com/shioyama/mobility/blob/99579bb5f3bf9b3588fe5e7319bcb1b9e83131ec/lib/rails/generators/mobility/backend_generators/base.rb

[shioyama]

Honestly, this feels like a Rails bug.

[shioyama]

Fixed in 1.2.5.