It would not trigger the same bug. But since it's a multi-threaded server, it will exercise arbitrary code (Rails core, your app, depended-on gems) in a concur

It would not trigger the same bug. But since it's a multi-threaded server, it will exercise arbitrary code (Rails core, your app, depended-on gems) in a concurrent manner. This can unmask race conditions that wouldn't manifest themselves under a single-threaded environment. ...that's been my experience with Puma - brilliant server in itself, somewhat risky approach when considering the Ruby ecosystem.