Axel Vermeil

Hi @mateioprea ! At the moment, we don't support [Service Accounts](https://developers.google.com/google-ads/api/docs/oauth/service-accounts). We've actually never used them, so we're not totally sure how they should work. PRs welcome ;) That said,...

Hi @alessandro-aglietti , Thanks for taking the time to work on this! Yes, the solution you propose sounds good :)

Getting this same error as well: ``` ReplyError: ERR SETTINGS_KEY_NOT_FOUND at parseError (/usr/api/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/usr/api/node_modules/redis-parser/lib/parser.js:302:14) { command: 'EVALSHA', args: [ '8bd3e064b718321194a8df49c69e48fd0ffb4dcd', 8, 'b_builtwith_throttler_settings', 'b_builtwith_throttler_job_weights', 'b_builtwith_throttler_job_expirations', 'b_builtwith_throttler_job_clients', 'b_builtwith_throttler_client_running', 'b_builtwith_throttler_client_num_queued', 'b_builtwith_throttler_client_last_registered',...

We're also affected by this bug.

That's interesting... is there much of a cost to calling ```sql CREATE TABLE IF NOT EXISTS oxen_queue ``` for every instance of Oxen?

True, that'd be convenient! PRs welcome ;). Bonus if you can do it without modifying the schema!

Yeah, it's absolutely massive and overkill for what it is. The issue stems from the fact that google-ads-node is built using Google's Bazel, which (using protobufjs) generates tons of JS...