Soundcloud API rate limit

[JKatzwinkel]

In #247, I attempted to make travis happy, but travis is not happy :c

(neither is github actions for that matter)

As HTTP response code 429 is supposed to indicate a too many requests situation, I figured I go and generate a new API key. However:

But regardless of soundcloud not providing new keys at the moment, what seems kind of puzzling is that both travis and (for the most part functionally identical) github CI setups fail, but I can run nosetests locally as much as I please!!?

Any ideas about how we can make travis happy?

[viatekh]

it was inevitable that requests max out. those keys are everywhere now.

i've reached out to soundcloud to ask about applications. best case scenario, applications open up again, and we can write a little guide to show people how to generate their own API keys, and add them to the script.

worst case scenario, we lose access to the API as SC works out what we're doing with them (i imagine this is against TOS of the site to be honest)

[JKatzwinkel]

Thanks for taking action! Hopefully soundcloud will get their registration process back on track soon.

I still don't understand why both CI setups (travis & github actions) consistently fail due to exceeded quota, BUT if I run nosetests locally on my machine, no such problems occur...?

[meta-boy]

it was inevitable that requests max out. those keys are everywhere now.

I would have volunteered to give out my keys but they would ended up the same way

[markddavidoff]

:(