You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Puma users frequently experience problems with Byebug which are solved by increasing puma's worker timeout. The worker timeout is intended to kill Puma workers which do not periodically send the master process a heartbeat reply.
The problem is:
The heartbeat is implemented in Ruby
Byebug's c-extension is not GVL-aware
The heartbeat never gets sent, so Puma kills the worker, thus killing the debug session.
Puma users frequently experience problems with Byebug which are solved by increasing puma's worker timeout. The worker timeout is intended to kill Puma workers which do not periodically send the master process a heartbeat reply.
The problem is:
Workaround is here: rails/rails#40503
The text was updated successfully, but these errors were encountered: