pebblecode / tricklrapp.com

Trickle out tweets over time
http://tricklrapp.com
0 stars 0 forks source link

Tweets not sent #97

Open taktran opened 10 years ago

taktran commented 10 years ago

@tricklr @pebblecode Help! My tweets are caught in the Tricklr. They flash in my queue for a second with negative times, then disappear.

@facts_n_quotes (id 2837)

May be related to #95

TODO

taktran commented 10 years ago

Get message The Twitter REST API v1 is no longer active. Please migrate to API v1.1. https://dev.twitter.com/docs/api/1.1/overview.

http://tricklrapp.com/resque/failed?start=20751

taktran commented 10 years ago

Also https://blog.twitter.com/2013/planning-for-api-v1-retirement

taktran commented 10 years ago

Trying to upgrade twitter gem, but get a clash of dependencies:

Bundler could not find compatible versions for gem "faraday":
  In Gemfile:
    tinder (= 1.9.2) ruby depends on
      faraday (< 0.9, >= 0.7.4) ruby

    twitter (~> 5.8.0) ruby depends on
      faraday (0.9.0)

Digging into tinder, it seems like it hasn't upgraded to the new version of faraday yet. See https://github.com/collectiveidea/tinder/pull/57/files.

Also, tinder relies on faraday_middleware issue which has a bit of work before it can be upgraded.

taktran commented 10 years ago

Tried downgrading twitter gem to 5.5.1 (which supports faraday 0.8), but get json dependency errors:

~/W/D/tricklrapp.com(master*)$ bundle update twitter
Fetching gem metadata from http://rubygems.org/........
Fetching gem metadata from http://rubygems.org/..
Bundler could not find compatible versions for gem "json":
  In snapshot (Gemfile.lock):
    json (1.7.7)

  In Gemfile:
    twitter (~> 5.5.1) ruby depends on
      json (~> 1.8) ruby

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.
taktran commented 10 years ago

Currently updated the master branch with the new twitter gem (5.8.0), however I had to comment out tinder for the time being due to the twitter gem dependency clashes with faraday.

Tried to deploy this, but there seems to be issues with capistrano too:

bundle exec cap staging deploy
cap aborted!
cannot load such file -- config/deploy
/Users/ttt/Work/Dev/tricklrapp.com/Capfile:4:in `load'
/Users/ttt/Work/Dev/tricklrapp.com/Capfile:4:in `<top (required)>'
/Users/ttt/Work/Dev/tricklrapp.com/vendor/bundle/ruby/1.9.1/gems/capistrano-3.1.0/lib/capistrano/application.rb:24:in `load_rakefile'
/Users/ttt/Work/Dev/tricklrapp.com/vendor/bundle/ruby/1.9.1/gems/capistrano-3.1.0/lib/capistrano/application.rb:15:in `run'
/Users/ttt/Work/Dev/tricklrapp.com/vendor/bundle/ruby/1.9.1/gems/capistrano-3.1.0/bin/cap:3:in `<top (required)>'
/Users/ttt/Work/Dev/tricklrapp.com/vendor/bundle/ruby/1.9.1/bin/cap:23:in `load'
/Users/ttt/Work/Dev/tricklrapp.com/vendor/bundle/ruby/1.9.1/bin/cap:23:in `<main>'
(See full trace by running task with --trace)
rake aborted!
Command failed with status (1): [bundle exec cap staging deploy...]
/Users/ttt/Work/Dev/tricklrapp.com/lib/tasks/shipit.rake:43:in `branch!'
/Users/ttt/Work/Dev/tricklrapp.com/lib/tasks/deploy.rake:91:in `block in <top (required)>'
/Users/ttt/Work/Dev/tricklrapp.com/lib/tasks/deploy.rake:101:in `block in <top (required)>'
Tasks: TOP => deploy

to be continued...