Unable to upload content of tailored audience via ton_upload (again)

alex_coppens · 2016-10-13T11:45:08.640Z

The logs can be found here:

gist.github.com

https://gist.github.com/francois/f0c054aed94a7dd6e440b87c31e3ec14

gistfile1.txt

[DEBUG] sync-ad-network-audiences:26617 - Uploading chunk starting at 160.0M of 182.8M (87.5%) of /var/tmp/seevibes/twitter-upload/f57c1326-013a-4f38-aecf-ebb9ac869c92/_09_06_Bird_Office_FR_TW_New_Tech_News_1476304379.csv-hashed
[INFO ] sync-ad-network-audiences:26617 - Send: PUT https://ton.twitter.com/1.1/ton/data/ta_partner/152397343/kYuMV-EpmnbWRYz.txt?resumable=true&resumeId=258648
[INFO ] sync-ad-network-audiences:26617 - Header: accept-encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3
[INFO ] sync-ad-network-audiences:26617 - Header: accept: */*
[INFO ] sync-ad-network-audiences:26617 - Header: user-agent: twitter-ads version: 1.0.0 platform: ruby 2.2.5 (x86_64-linux-gnu) (OAuth gem v0.4.7)
[INFO ] sync-ad-network-audiences:26617 - Header: content-type: text/plain
[INFO ] sync-ad-network-audiences:26617 - Header: content-length: 0
[INFO ] sync-ad-network-audiences:26617 - Header: content-range: bytes 167772160-191725624/191725625
[INFO ] sync-ad-network-audiences:26617 - Header: authorization: OAuth oauth_body_hash="o16h%2BuPdt9ZjkcTbYGQuV8BHux4%3D", oauth_consumer_key="---", oauth_nonce="HZ2WkrUNN7bRts7TnEQBwdgl2nao3bQmP74Z3BIgw4s", oauth_signature="x6dW5PlytwMOeG9mnPabXNoHrQM%3D", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1476304646", oauth_token="152397343-F2sSm9WuEcb7luVmppKrEXO4y6QDQzb6wkrxBgz0", oauth_version="1.0"
[INFO ] sync-ad-network-audiences:26617 - Body: **OMITTED**

This file has been truncated. show original

To reproduce the problem:

Create a tailored audience using the apis (we are using https://github.com/twitterdev/twitter-ruby-ads-sdk )
Upload a file containing TWITTER_IDS using the Ton-upload.
when assigning the file to the tailored audience, we are getting a BadRequest error ( “INVALID_PARAMETER”)

It’s not the first time we noticed that error, it disappeared for a while but now is reappearing…

JBabichJapan · 2016-11-01T06:05:49.030Z

Hi,

Sorry for delay in replying here. I was able to repro this issue with latest set of Python SDK code and I’m investigating what’s going on but generally when it doubt we would use ton_upload script with --trace as shown:

ton_upload --trace -m upload -b ta_partner -f ~/list.txt

github.com

twitterdev/ton-upload/blob/master/ton_upload

#!/usr/bin/env ruby -KU -rubygems

# The TON API allows OAuth 1.0A or with whitelisting OAuth 2 (application-only auth)
# Default is OAuth 1.0A for all applications accessing the TON API.
#
# Documentation for doing application-only auth using the Twitter API:
#   https://dev.twitter.com/docs/auth/3-legged-authorization
#   https://dev.twitter.com/docs/auth/application-only-auth and
#   https://dev.twitter.com/docs/api/1.1/post/oauth2/token
#
# This script uses the .twurlrc file managed by https://github.com/twitter/twurl

require 'bundler/setup'

require 'digest/md5'
require 'json'
require 'logger'
require 'mime/types'
require 'rest-client'
require 'twurl'

This file has been truncated. show original

If that works and SDK does not, I expect it is simply a bug with SDK that needs to be fixed.

If even this is not working and you are blocked from uploading data, definitely please let us know.

Thanks,

John

alex_coppens · 2016-11-04T15:07:03.651Z

Hello John,

I was wondering if you had any updates on that issue? We are using ton_upload.rb as our library and the logs we provided are from the trace. There is a 201 code returned after upload so the TON upload is not what breaks but the step after (assigning the file to the audience).

alex_coppens · 2016-11-21T19:12:57.527Z

Hello again,

I wanted to mention that problem disappeared on Friday and reappeared today. Our codebase didn’t change over the weekend.

Alex

JBabichJapan · 2016-11-25T04:25:28.516Z

Hey Alex,

Sorry I was investigating this issue off and on over the past week and I think I know what’s going on but haven’t yet confirmed why this regressed from when the SDK was originally released.

In the meantime, I also found out that the multi-chunk upload limit within the SDK is set at 1MB (so any file bigger than 1MB gets sent to multichunk instead of single chunk) - where it could be up to 64MB instead. If your audiences are < 64MB (I think most of them are) this problem shouldn’t block you anymore after the latest pull request I just submitted gets merged in. I would encourage you to help submit and review pull requests because we are looking for more active contributors to these SDKs.

The multichunk issue causing BadRequest above seems to be that input_file_path sent to tailored_audience_changes includes parameters, if passed the version without parameters it should work fine.

Thanks,

John