opensafely-core / opensafely-core/reports
CI test run can be flaky due to exceeding GitHub API limits
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 5
Description
The tests in CI do pass without any change. But when running the tests, I did get for one run:
FAILED tests/reports/test_views.py::test_report_view_last_updated - osgithub.github.GithubAPIException: {"message": "API rate limit exceeded for (redacted IP address). (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)", "documentation_url": "https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting"}
The environment variables are configured in the test workflow. The GITHUB_TOKEN environment variable is unset as this commit.
There might be a good reason why we leave this unset, but it's not documented in the commit history or PR thread.
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
Start with tests/reports/test_views.py::test_report_view_last_updated and inspect the test workflow's environment variables. Review commit 7fa98d3101aa1d79db04b4d0b1fa398611010492 and its surrounding history to understand why GITHUB_TOKEN is unset. Done means the rate-limit cause and intended CI configuration or documentation are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, python
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100