Starting solid_queue on development erroring after upgrading Rails to 8.0

[sebaherrera07]

I'm upgrading my web app to Rails 8.0, and it's a small app so I'm running the latest version of Ruby (3.3.6) and all gems. I also try to default to all autogenerated Rails configs as much as possible.

I already had Solid Queue up and running in production and development by calling plugin :solid_queue in puma.rb.

After upgrading Rails, when running rails s locally I'm getting the following error:

=> Booting Puma
=> Rails 8.0.0 application starting in development 
=> Run `bin/rails server --help` for more startup options
Puma starting in single mode...
* Puma version: 6.4.3 (ruby 3.3.6-p108) ("The Eagle of Durango")
*  Min threads: 3
*  Max threads: 3
*  Environment: development
*          PID: 38891
* Listening on http://127.0.0.1:3000
* Listening on http://[::1]:3000
Use Ctrl-C to stop
objc[39018]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called.
objc[39018]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
Detected Solid Queue has gone away, stopping Puma...
- Gracefully stopping, waiting for requests to finish
=== puma shutdown: 2024-11-11 19:01:44 -0300 ===
- Goodbye!
Exiting

If I run OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES rails s it does work.

Any ideas what might be wrong with my setup?

[rosa]

Hey @sebaherrera07, are you using PostgreSQL in macOS? It sounds like a known bug with pg in macOS.