xdevplatform/twitter-ruby-ads-sdk

Socket error when making async HTTP request to Twitter Ads API multiple times

Closed this issue · 1 comments

Issue Type: Bug

Description:

Try to make async HTTP request to Twitter Ads API multiple times but eventually hit a socket error. Not sure how to resolve it. This prevented Twitter from processing all the jobs.

Expected Result:

Continue processing the Twitter job via async HTTP request.

Actual Result:

SocketError: #<SocketError: getaddrinfo: Name or service not known>
/usr/local/lib/ruby/2.1.0/net/http.rb:879:in initialize' /usr/local/lib/ruby/2.1.0/net/http.rb:879:inopen'
/usr/local/lib/ruby/2.1.0/net/http.rb:879:in block in connect' /usr/local/lib/ruby/2.1.0/timeout.rb:90:inblock in timeout'
/usr/local/lib/ruby/2.1.0/timeout.rb:100:in call' /usr/local/lib/ruby/2.1.0/timeout.rb:100:intimeout'
/usr/local/lib/ruby/2.1.0/net/http.rb:878:in connect' /usr/local/lib/ruby/2.1.0/net/http.rb:863:indo_start'
/usr/local/lib/ruby/2.1.0/net/http.rb:852:in start' /usr/local/lib/ruby/2.1.0/net/http.rb:1375:inrequest'
/usr/local/bundle/gems/twitter-ads-1.0.0/lib/twitter-ads/http/request.rb:75:in oauth_request' /usr/local/bundle/gems/twitter-ads-1.0.0/lib/twitter-ads/http/request.rb:57

Steps to Reproduce:

Make async HTTP request to Twitter Ads API multiple times.

Closing this for now. Let us know if you still see this issue.