John Bachir

i have a version of my app working with this branch, with just the dependency name changed https://github.com/anycable/graphql-anycable/compare/master...jjb:graphql-anycable:patch-1

Thanks! However I can't use it because my system still requires client-provided channel identifiers 😅 any chance you could bring that back, and take it out in 2.0?

wow, a version just for me! 😄 thanks!

this array was generated with `"test"`, which i removed ```ruby if !defined?(Spring) && [nil, "development"].include?(ENV["RAILS_ENV"]) ```

i had this problem too, described here https://github.com/mperham/sidekiq/issues/1514 the problem goes away with 01861d9bba163a4e7af0cac8760067624e0a9ca0

/cc @jmettraux

yep: https://docs.ruby-lang.org/en/master/signals_rdoc.html#label-Unsafe+methods+to+call+in+Signal.trap+blocks

Thanks for your thoughts @jmettraux - sorry for confusion, I don't think anything needs to be changed in rufus, I just thought you might think this is sort of interesting...

Thanks! but even if it is, i don't think it would be rufus' responsibility to change - was just looping you in in case you had some insights on rufus...

``` ruby-clock-2.0.1/lib/ruby-clock.rb:28:in `write': deadlock; recursive locking (ThreadError) gems/ruby-clock-2.0.1/lib/ruby-clock.rb:28:in `puts' gems/ruby-clock-2.0.1/lib/ruby-clock.rb:28:in `puts' gems/ruby-clock-2.0.1/lib/ruby-clock.rb:28:in `shutdown' gems/ruby-clock-2.0.1/lib/ruby-clock.rb:37:in `block (2 levels) in listen_to_signals' gems/ruby-clock-2.0.1/lib/ruby-clock.rb:53:in `write' gems/ruby-clock-2.0.1/lib/ruby-clock.rb:53:in `puts' gems/ruby-clock-2.0.1/lib/ruby-clock.rb:53:in `puts' gems/ruby-clock-2.0.1/lib/ruby-clock.rb:53:in `run_jobs' gems/ruby-clock-2.0.1/exe/clock:84:in `' ```