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

Undefined method scheduler #9

Open
jorgefuertes opened this issue Jun 29, 2016 · 0 comments
Open

Undefined method scheduler #9

jorgefuertes opened this issue Jun 29, 2016 · 0 comments

Comments

@jorgefuertes
Copy link

I don't know if I'm doing something wrong but I feel like if I've followed the readme step by step and I got this error:

DEBUG -       GET (0.0019s) /ws/channel - 200 OK
DEBUG -  Connection openned as user: 5cbf3d87-4919-4155-b314-66a751556f26 on channel: channel.
[error] unhandled exception: undefined method `scheduler' for #<Libuv::Loop:0x3fe6965f9490 NT=0> (error - q_resolve_cb)
~/.rvm/gems/ruby-2.2.1/gems/padrino-websockets-0.1.1/lib/padrino-websockets/spider-gazelle/event-manager.rb:37:in `on_open'
~/.rvm/gems/ruby-2.2.1/gems/websocket-driver-0.6.4/lib/websocket/driver/event_emitter.rb:39:in `call'
~/.rvm/gems/ruby-2.2.1/gems/websocket-driver-0.6.4/lib/websocket/driver/event_emitter.rb:39:in `block in emit'
~/.rvm/gems/ruby-2.2.1/gems/websocket-driver-0.6.4/lib/websocket/driver/event_emitter.rb:38:in `each'
~/.rvm/gems/ruby-2.2.1/gems/websocket-driver-0.6.4/lib/websocket/driver/event_emitter.rb:38:in `emit'
~/.rvm/gems/ruby-2.2.1/gems/websocket-driver-0.6.4/lib/websocket/driver.rb:131:in `open'
~/.rvm/gems/ruby-2.2.1/gems/websocket-driver-0.6.4/lib/websocket/driver.rb:97:in `start'
~/.rvm/gems/ruby-2.2.1/gems/padrino-websockets-0.1.1/lib/padrino-websockets/spider-gazelle/routing.rb:29:in `block (2 levels) in websocket'
~/.rvm/gems/ruby-2.2.1/gems/libuv-2.0.8/lib/libuv/q.rb:109:in `call'
~/.rvm/gems/ruby-2.2.1/gems/libuv-2.0.8/lib/libuv/q.rb:109:in `block in then'
~/.rvm/gems/ruby-2.2.1/gems/libuv-2.0.8/lib/libuv/q.rb:200:in `call'
~/.rvm/gems/ruby-2.2.1/gems/libuv-2.0.8/lib/libuv/q.rb:200:in `block in then'
~/.rvm/gems/ruby-2.2.1/gems/libuv-2.0.8/lib/libuv/loop.rb:103:in `call'
~/.rvm/gems/ruby-2.2.1/gems/libuv-2.0.8/lib/libuv/loop.rb:103:in `process_item'
~/.rvm/gems/ruby-2.2.1/gems/libuv-2.0.8/lib/libuv/loop.rb:96:in `block in process_queue_cb'
~/.rvm/gems/ruby-2.2.1/gems/libuv-2.0.8/lib/libuv/loop.rb:95:in `times'
~/.rvm/gems/ruby-2.2.1/gems/libuv-2.0.8/lib/libuv/loop.rb:95:in `process_queue_cb'
~/.rvm/gems/ruby-2.2.1/gems/libuv-2.0.8/lib/libuv/loop.rb:89:in `next_tick_cb'
~/.rvm/gems/ruby-2.2.1/gems/libuv-2.0.8/lib/libuv/timer.rb:81:in `call'
~/.rvm/gems/ruby-2.2.1/gems/libuv-2.0.8/lib/libuv/timer.rb:81:in `on_timer'
~/.rvm/gems/ruby-2.2.1/gems/libuv-2.0.8/lib/libuv/mixins/listener.rb:14:in `dispatch_callback'
~/.rvm/gems/ruby-2.2.1/gems/libuv-2.0.8/lib/libuv/mixins/listener.rb:19:in `block in define_callback'
~/.rvm/gems/ruby-2.2.1/gems/libuv-2.0.8/lib/libuv/loop.rb:141:in `call'
~/.rvm/gems/ruby-2.2.1/gems/libuv-2.0.8/lib/libuv/loop.rb:141:in `run'
~/.rvm/gems/ruby-2.2.1/gems/libuv-2.0.8/lib/libuv/loop.rb:141:in `run'
~/.rvm/gems/ruby-2.2.1/gems/spider-gazelle-2.0.2/lib/spider-gazelle/spider.rb:269:in `load_gazelle_thread'
~/.rvm/gems/ruby-2.2.1/gems/spider-gazelle-2.0.2/lib/spider-gazelle/spider.rb:249:in `block (2 levels) in load_gazelles'
DEBUG -  Calling event: ping as user: 5cbf3d87-4919-4155-b314-66a751556f26 on channel channel.
DEBUG -  {"some"=>"data"}
 WARN -  PING: {"some"=>"data"}
 WARN -  SESS: "5cbf3d87-4919-4155-b314-66a751556f26"
DEBUG -  Sending message: {:pong=>true, :data=>{"some"=>"data"}} to user: 5cbf3d87-4919-4155-b314-66a751556f26 on channel: ping. Message
ERROR -  Error while running the event handler
ERROR -  undefined method `[]' for nil:NilClass
ERROR -  ~/.rvm/gems/ruby-2.2.1/gems/padrino-websockets-0.1.1/lib/padrino-websockets/base-event-manager.rb:150:in `send_message'

Please, can anyone confirm if its my fault or a bug with the last padrino, Spider-Gazelle or something?

Thanks in advance.

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