Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"can't be called from trap context" shutdown issue on Ruby 2.0.0 #98

Closed
jmettraux opened this issue Feb 13, 2014 · 0 comments
Closed

"can't be called from trap context" shutdown issue on Ruby 2.0.0 #98

jmettraux opened this issue Feb 13, 2014 · 0 comments
Assignees

Comments

@jmettraux
Copy link
Owner

Initially reported at: http://stackoverflow.com/questions/21733308/gracefully-stop-rufus-scheduler-on-heroku-worker

test code: https://gist.github.com/jmettraux/a4c00374f58e9f7affa8

output:

/home/jmettraux/w/rufus-scheduler/lib/rufus/scheduler/job_array.rb:74:
  in `synchronize': can't be called from trap context (ThreadError)
    from /home/jmettraux/w/rufus-scheduler/lib/rufus/scheduler/job_array.rb:74:in `to_a'
    from /home/jmettraux/w/rufus-scheduler/lib/rufus/scheduler.rb:276:in `jobs'
    from /home/jmettraux/w/rufus-scheduler/lib/rufus/scheduler.rb:127:in `shutdown'
    from t.rb:8:in `block in <main>'
    from t.rb:18:in `call'
    from t.rb:18:in `sleep'
    from t.rb:18:in `<main>'

https://www.ruby-forum.com/topic/4411227

@jmettraux jmettraux self-assigned this Feb 13, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant