Skip to content

t stream timeline, errors. ubuntu 12.04 #41

Closed
msagebiel opened this Issue May 10, 2012 · 10 comments

8 participants

@msagebiel

mark@ubuntu:~$ t stream timeline
/var/lib/gems/1.8/gems/tweetstream-1.1.5/lib/tweetstream/client.rb:458:in parser_from': undefined methodadapter=' for MultiJson:Module (NoMethodError)
from /var/lib/gems/1.8/gems/tweetstream-1.1.5/lib/tweetstream/client.rb:41:in json_parser'
from /var/lib/gems/1.8/gems/tweetstream-1.1.5/lib/tweetstream/client.rb:36:in
initialize'
from /var/lib/gems/1.8/gems/t-0.9.6/lib/t/stream.rb:107:in new'
from /var/lib/gems/1.8/gems/t-0.9.6/lib/t/stream.rb:107:in
client'
from /var/lib/gems/1.8/gems/t-0.9.6/lib/t/stream.rb:67:in timeline'
from /var/lib/gems/1.8/gems/thor-0.15.2/lib/thor/task.rb:27:in
send'
from /var/lib/gems/1.8/gems/thor-0.15.2/lib/thor/task.rb:27:in run'
from /var/lib/gems/1.8/gems/thor-0.15.2/lib/thor/invocation.rb:120:in
invoke_task'
from /var/lib/gems/1.8/gems/thor-0.15.2/lib/thor.rb:275:in dispatch'
from /var/lib/gems/1.8/gems/thor-0.15.2/lib/thor/invocation.rb:109:in
send'
from /var/lib/gems/1.8/gems/thor-0.15.2/lib/thor/invocation.rb:109:in invoke'
from /var/lib/gems/1.8/gems/thor-0.15.2/lib/thor.rb:213:in
stream'
from /var/lib/gems/1.8/gems/thor-0.15.2/lib/thor/task.rb:27:in send'
from /var/lib/gems/1.8/gems/thor-0.15.2/lib/thor/task.rb:27:in
run'
from /var/lib/gems/1.8/gems/thor-0.15.2/lib/thor/invocation.rb:120:in invoke_task'
from /var/lib/gems/1.8/gems/thor-0.15.2/lib/thor.rb:275:in
dispatch'
from /var/lib/gems/1.8/gems/thor-0.15.2/lib/thor/base.rb:408:in start'
from /var/lib/gems/1.8/gems/t-0.9.6/bin/t:11
from /usr/local/bin/t:19:in
load'
from /usr/local/bin/t:19

@jphpsf
jphpsf commented May 10, 2012

Hi,

I use Ubuntu and I don't have the issue. Note that I am still running 11.10, I have not upgraded to 12.04. I am planning to upgrade in the next few days, so I will try to see if I have the issue as well.

Also note, that I am running ruby 1.9.3 and it seems that Ubuntu 12.04 ships with ruby 1.8. I have been running brightbox recent ruby packages which brings ruby 1.9.3 to Ubuntu. It's really easy to install:
http://blog.brightbox.co.uk/posts/next-generation-ruby-packages-for-ubuntu
http://wiki.brightbox.co.uk/docs:ruby-ng

Would you mind trying this out?

@msagebiel

thank you, tried it on lucid. compiled the first time and going well.
t stream timeline (on lucid) (12.04 build ->tomorrow)

Faraday: you may want to install system_timer for reliable timeouts

tweets

terminate called after throwing an instance of 'std::runtime_error'
what(): Encryption not available on this event-machine
Abgebrochen

@yourcelf

I'm getting a slightly different error attempting to stream using Ubuntu 12.04: HTTP::Parser::Error. The initial list of tweets works fine; but each time a new tweet arrives, t crashes out with this error. I've tried with both ruby1.8 and ruby1.9.1. The output of the error for 1.9.1:

/var/lib/gems/1.9.1/gems/twitter-stream-0.1.15/lib/twitter/json_stream.rb:120:in `<<': Could not parse data entirely (HTTP::Parser::Error)
    from /var/lib/gems/1.9.1/gems/twitter-stream-0.1.15/lib/twitter/json_stream.rb:120:in `receive_data'
    from /var/lib/gems/1.9.1/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run_machine'
    from /var/lib/gems/1.9.1/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run'
    from /var/lib/gems/1.9.1/gems/tweetstream-1.1.5/lib/tweetstream/client.rb:337:in `start'
    from /var/lib/gems/1.9.1/gems/tweetstream-1.1.5/lib/tweetstream/client.rb:127:in `userstream'
    from /var/lib/gems/1.9.1/gems/t-0.9.6/lib/t/stream.rb:81:in `timeline'
    from /var/lib/gems/1.9.1/gems/thor-0.15.2/lib/thor/task.rb:27:in `run'
    from /var/lib/gems/1.9.1/gems/thor-0.15.2/lib/thor/invocation.rb:120:in `invoke_task'
    from /var/lib/gems/1.9.1/gems/thor-0.15.2/lib/thor.rb:275:in `dispatch'
    from /var/lib/gems/1.9.1/gems/thor-0.15.2/lib/thor/invocation.rb:109:in `invoke'
    from /var/lib/gems/1.9.1/gems/thor-0.15.2/lib/thor.rb:213:in `block in subcommand'
    from /var/lib/gems/1.9.1/gems/thor-0.15.2/lib/thor/task.rb:27:in `run'
    from /var/lib/gems/1.9.1/gems/thor-0.15.2/lib/thor/invocation.rb:120:in `invoke_task'
    from /var/lib/gems/1.9.1/gems/thor-0.15.2/lib/thor.rb:275:in `dispatch'
    from /var/lib/gems/1.9.1/gems/thor-0.15.2/lib/thor/base.rb:408:in `start'
    from /var/lib/gems/1.9.1/gems/t-0.9.6/bin/t:11:in `<top (required)>'
    from /usr/local/bin/t:19:in `load'
    from /usr/local/bin/t:19:in `<main>'
@chrismatthieu

Getting the HTTP::Parser::Error on a new Mac deploy. Here's the error output:

/Users/chris/.rvm/gems/ruby-1.9.2-p318/gems/twitter-stream-0.1.15/lib/twitter/json_stream.rb:120:in <<': Could not parse data entirely (HTTP::Parser::Error)
from /Users/chris/.rvm/gems/ruby-1.9.2-p318/gems/twitter-stream-0.1.15/lib/twitter/json_stream.rb:120:in
receive_data'
from /Users/chris/.rvm/gems/ruby-1.9.2-p318/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in run_machine'
from /Users/chris/.rvm/gems/ruby-1.9.2-p318/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in
run'
from /Users/chris/.rvm/gems/ruby-1.9.2-p318/gems/tweetstream-1.1.5/lib/tweetstream/client.rb:337:in start'
from /Users/chris/.rvm/gems/ruby-1.9.2-p318/gems/tweetstream-1.1.5/lib/tweetstream/client.rb:127:in
userstream'
from /Users/chris/.rvm/gems/ruby-1.9.2-p318/gems/t-0.9.6/lib/t/stream.rb:81:in timeline'
from /Users/chris/.rvm/gems/ruby-1.9.2-p318/gems/thor-0.15.2/lib/thor/task.rb:27:in
run'
from /Users/chris/.rvm/gems/ruby-1.9.2-p318/gems/thor-0.15.2/lib/thor/invocation.rb:120:in invoke_task'
from /Users/chris/.rvm/gems/ruby-1.9.2-p318/gems/thor-0.15.2/lib/thor.rb:275:in
dispatch'
from /Users/chris/.rvm/gems/ruby-1.9.2-p318/gems/thor-0.15.2/lib/thor/invocation.rb:109:in invoke'
from /Users/chris/.rvm/gems/ruby-1.9.2-p318/gems/thor-0.15.2/lib/thor.rb:213:in
block in subcommand'
from /Users/chris/.rvm/gems/ruby-1.9.2-p318/gems/thor-0.15.2/lib/thor/task.rb:27:in run'
from /Users/chris/.rvm/gems/ruby-1.9.2-p318/gems/thor-0.15.2/lib/thor/invocation.rb:120:in
invoke_task'
from /Users/chris/.rvm/gems/ruby-1.9.2-p318/gems/thor-0.15.2/lib/thor.rb:275:in dispatch'
from /Users/chris/.rvm/gems/ruby-1.9.2-p318/gems/thor-0.15.2/lib/thor/base.rb:408:in
start'
from /Users/chris/.rvm/gems/ruby-1.9.2-p318/gems/t-0.9.6/bin/t:11:in <top (required)>'
from /Users/chris/.rvm/gems/ruby-1.9.2-p318/bin/t:19:in
load'
from /Users/chris/.rvm/gems/ruby-1.9.2-p318/bin/t:19:in `

'

@sferik
Owner
sferik commented May 12, 2012

These are two separate issues. I believe the HTTP::Parser::Error is the result of me using an unreleased version of tweetstream in development. I'm working closely with @spagalloco to ship an awesome tweetstream 2.0 release, but that's at least a few days away.

As for this Ubuntu issue, I'm currently on a Mac so I can't reproduce or debug the problem. If someone has an Ubuntu machine that they'd like to give me access to, here is my SSH public key: https://gist.github.com/2663771

This blog post may also be helpful: http://www.memoefix.com/?p=208 (it's written in French but Google Translate does a pretty good job converting it to English)

@sferik
Owner
sferik commented May 12, 2012

By the way, the original error makes it look like an outdated version of MultiJson is being used. Try upgrading to MultiJson 1.3.5 and let me know if the problem persists.

@stve
Collaborator
stve commented May 12, 2012

The backtrace coming from twitter-stream looks the same as the one referenced in voloko/twitter-stream#27 I don't think they've released a fix yet.

@vijaydev

Can confirm that the original error is fixed by updating MultiJson to 1.3.5. (Ubuntu 11.04)

@sferik sferik closed this May 15, 2012
@ngrichyj4

yes, updating multi_json 1.3.5 fixed issue for me.

@msagebiel

:1,$ s/(\d+) (\w+) *(\d+) (\d\d:\d\d) @(\w+)/http:\/\/twitter.com\/\5\/status\/\1 \2 \3 \4/g urlopener.com
found a way to get the twitter links in vim(ok api stuff would be easier)
it works for couple of hundreds, 200 Tabs in Firefox is ok.
t geturl id
would be good :)
or some command to get activity or who favs and RT you.
take care

t activity
t tweetsRT
t tweetsfaved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.