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
If a Sig-Int is sent to the Worker-Dispatcher under Ruby >= 2.0.0, Ruby reports a 'can't be called from trap context'-Error.
It seems, that Ruby 2.0 tries to be more thread-safe and raise an exception, if something is called which could cause a deadlock.
The workaround could be, putting the problematic code (like writing to a DB or to a Log-File) inside a new thread.
The text was updated successfully, but these errors were encountered:
If a Sig-Int is sent to the Worker-Dispatcher under Ruby >= 2.0.0, Ruby reports a 'can't be called from trap context'-Error.
It seems, that Ruby 2.0 tries to be more thread-safe and raise an exception, if something is called which could cause a deadlock.
The workaround could be, putting the problematic code (like writing to a DB or to a Log-File) inside a new thread.
The text was updated successfully, but these errors were encountered: