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

Angelo crashes using reel 0.6.x #52

Closed
mighe opened this issue Apr 7, 2015 · 12 comments
Closed

Angelo crashes using reel 0.6.x #52

mighe opened this issue Apr 7, 2015 · 12 comments

Comments

@mighe
Copy link

mighe commented Apr 7, 2015

Hi @kenichi, I was trying angelo with reel 0.6.0.pre1 and I get the following error:

NameError: uninitialized constant WebSocket::Message
    /xxx/angelo-ef0d4892d865/lib/angelo/base.rb:274:in `block (3 levels) in <class:Base>'
    /xxx//angelo-ef0d4892d865/lib/angelo/stash.rb:88:in `block in all_each'
    /xxx/angelo-ef0d4892d865/lib/angelo/stash.rb:86:in `each'
    /xxx/angelo-ef0d4892d865/lib/angelo/stash.rb:86:in `all_each'
    /xxx/angelo-ef0d4892d865/lib/angelo/base.rb:273:in `block (2 levels) in <class:Base>'

the problem is here: the code is using a class from the old websocket parser, that has been removed with the websocket-driver integration.

@kenichi
Copy link
Owner

kenichi commented Apr 7, 2015

ah, it looks like the new websocket-driver stuff does not expose the driver. since websocket-driver has its own ping, we should attempt to use that, eh?

@kenichi
Copy link
Owner

kenichi commented Apr 7, 2015

whoa, the new stuff depends on rack and uses Rack::MockRequest?

@digitalextremist
Copy link
Contributor

I see this too, and it bothered me. It's coming over by websocket-driver as you said. I've not wanted Rack anywhere near Reel or any DSL it supports. I will look into this also.

@mighe
Copy link
Author

mighe commented Apr 8, 2015

@digitalextremist do you think it could be useful to have a ping method exposed by Reel?
At the moment the only way @kenichi has is to use directly a Reel dependency and this could lead to unexpected problems in the future (like this one).
If pinging a websocket is a useful feature for many developers, having it integrated in Reel is probably the best thing.

@digitalextremist
Copy link
Contributor

@mighe we can expose ping ( forwarding to ping on @driver ) no problem.

@kenichi
Copy link
Owner

kenichi commented Apr 8, 2015

my immediate fix was to add :driver to the attr_accessor list, but then i saw the mockrequest and went down a rabbit hole of trying to make reel work without that.

@kenichi
Copy link
Owner

kenichi commented Apr 8, 2015

@digitalextremist 👍

@digitalextremist
Copy link
Contributor

Yeah I am going to make it work without Rack again. I swear there should be a C in front of Rack because every now and then someone keeps getting us hooked again. And it's all in good fun and everyone is having a rad party committing stuff, and then it's like 💣 Rack reappeared muahahaha

@kenichi
Copy link
Owner

kenichi commented Apr 8, 2015

@kenichi
Copy link
Owner

kenichi commented Apr 8, 2015

@digitalextremist
Copy link
Contributor

If we clean this up and make sure it's solid, I'll cut a pre2 with this in, while we wait on UNIX sockets.

@kenichi
Copy link
Owner

kenichi commented Jul 15, 2015

much has been done as a result of this issue, thanks @mighe.

@kenichi kenichi closed this as completed Jul 15, 2015
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

3 participants