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

Error "Could not parse data entirely (0 != 609) (HTTP::Parser::Error)" #179

Open
AlexWayfer opened this issue Feb 9, 2018 · 4 comments
Open

Comments

@AlexWayfer
Copy link

AlexWayfer commented Feb 9, 2018

☹️

#<Thread:0x000055ecc7024ef0@/home/alex/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/guard-livereload-2.5.2/lib/guard/livereload/reactor.rb:11 run> terminated with exception (report_on_exception is true):
Traceback (most recent call last):
	6: from /home/alex/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/guard-livereload-2.5.2/lib/guard/livereload/reactor.rb:11:in `block in initialize'
	5: from /home/alex/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/guard-livereload-2.5.2/lib/guard/livereload/reactor.rb:50:in `_start_reactor'
	4: from /home/alex/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/eventmachine-1.2.5/lib/eventmachine.rb:194:in `run'
	3: from /home/alex/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/eventmachine-1.2.5/lib/eventmachine.rb:194:in `run_machine'
	2: from /home/alex/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/em-websocket-0.5.1/lib/em-websocket/connection.rb:78:in `receive_data'
	1: from /home/alex/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/guard-livereload-2.5.2/lib/guard/livereload/websocket.rb:19:in `dispatch'
/home/alex/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/guard-livereload-2.5.2/lib/guard/livereload/websocket.rb:19:in `<<': Could not parse data entirely (0 != 609) (HTTP::Parser::Error)

Versions of dependencies:

  * guard (2.14.2)
  * guard-bundler (2.1.0)
  * guard-compat (1.2.1)
  * guard-livereload (2.5.2)
  * em-websocket (0.5.1)
  * multi_json (1.13.1)

Content of Guardfile:

guard :livereload do
  watch %r{views/.+\.erb$}
  watch %r{public/.+\.(css|js)$}
end
@AlexWayfer
Copy link
Author

Why 2.5.2 version in RubyGems (Feb 4, 2016) has other source without 3d2d962 from the same day?

And why there is 2.5.1 version in source code? https://github.com/guard/guard-livereload/blob/v2.5.2/lib/guard/livereload/version.rb#L3

Oh…

@AlexWayfer
Copy link
Author

AlexWayfer commented Feb 9, 2018

Version from master looks working for now.

UPD: Not…

#<Thread:0x000055ea7c71c9a8@/home/alex/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/bundler/gems/guard-livereload-38a3f5de16a3/lib/guard/livereload/reactor.rb:11 run> terminated with exception (report_on_exception is true):
Traceback (most recent call last):
	7: from /home/alex/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/bundler/gems/guard-livereload-38a3f5de16a3/lib/guard/livereload/reactor.rb:11:in `block in initialize'
	6: from /home/alex/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/bundler/gems/guard-livereload-38a3f5de16a3/lib/guard/livereload/reactor.rb:50:in `_start_reactor'
	5: from /home/alex/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/eventmachine-1.2.5/lib/eventmachine.rb:194:in `run'
	4: from /home/alex/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/eventmachine-1.2.5/lib/eventmachine.rb:194:in `run_machine'
	3: from /home/alex/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/em-websocket-0.5.1/lib/em-websocket/connection.rb:78:in `receive_data'
	2: from /home/alex/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/bundler/gems/guard-livereload-38a3f5de16a3/lib/guard/livereload/websocket.rb:14:in `dispatch'
	1: from /home/alex/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/bundler/gems/guard-livereload-38a3f5de16a3/lib/guard/livereload/websocket/dispatcher.rb:32:in `dispatch'
/home/alex/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/bundler/gems/guard-livereload-38a3f5de16a3/lib/guard/livereload/websocket/dispatcher.rb:32:in `<<': Could not parse data entirely (0 != 609) (HTTP::Parser::Error)

@AlexWayfer
Copy link
Author

It probably occurs only when the second connection appears…

@AlexWayfer
Copy link
Author

It probably occurs only when the second connection appears…

In the only one browser with multiple tabs everything is OK, but this exception occurs when you open the second browser (on another device) in parallel. 😢

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