Travis CI fails due to packrat not using api.github.com?
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 409
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
I have a project that uses travis CI and installs packages from github. It looks like it may be failing because packrat is trying to download sources from github.com rather than api.github.com see this line in restore.R. This might cause problems with github rate limits? I have GITHUB_PAT set. The Travis CI test is here.
(It looks like api.github.com is specified in available-updates.R.)
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 the referenced line in R/restore.R and compare it with the GitHub handling in available-updates.R. Reproduce the Travis CI case from ChowHub/paper-pattern-similarity, then determine whether the download endpoint causes the reported rate-limit problem. Done means the package source download behavior is consistent with the intended GitHub API usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- ci-cd, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100