![Why puma workers constantly hung, and how we fixed by discovering the bug of Ruby v2.5.8 and v2.6.6 | by Yohei Yoshimuta | ITNEXT Why puma workers constantly hung, and how we fixed by discovering the bug of Ruby v2.5.8 and v2.6.6 | by Yohei Yoshimuta | ITNEXT](https://miro.medium.com/v2/resize:fit:1200/1*-k5nqnm1RR0KelAZ5xHXfQ.png)
Why puma workers constantly hung, and how we fixed by discovering the bug of Ruby v2.5.8 and v2.6.6 | by Yohei Yoshimuta | ITNEXT
Puma 5.0.2, Rails 6.0.3.4 - "WARNING: Detected 1 Thread(s) started in app boot" · Issue #2421 · puma/puma · GitHub
![ruby - Rails logs do not show anything in terminal for Puma when I try to hit the URL: localhost:3000 - Stack Overflow ruby - Rails logs do not show anything in terminal for Puma when I try to hit the URL: localhost:3000 - Stack Overflow](https://i.stack.imgur.com/HG4ay.png)
ruby - Rails logs do not show anything in terminal for Puma when I try to hit the URL: localhost:3000 - Stack Overflow
![In Rails 7.0.0-alpha2, mobility and good_job seem to conflict using development puma web concurrency · Issue #549 · shioyama/mobility · GitHub In Rails 7.0.0-alpha2, mobility and good_job seem to conflict using development puma web concurrency · Issue #549 · shioyama/mobility · GitHub](https://user-images.githubusercontent.com/2021411/144530396-7caab2c5-f18c-4e94-86e8-68bdc7dbb2ff.png)