Miserlou / Miserlou/SoundScrape
Soundcloud API rate limit
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.4k
- Forks
- 143
- PR merge metrics
- No merged PRs in 30d
Description
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?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names Travis, GitHub Actions, and nosetests but no repository files or failing test are identified. Start by comparing the CI runs with local nosetests and inspect the requests receiving HTTP 429 responses. Done means the CI suite runs reliably without exceeding the SoundCloud API rate limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- api, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100