Rdatatable / Rdatatable/data.table
Restore linting of .Rraw files
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 3.9k
- Forks
- 1.1k
- Avg merge
- 14h 4m
- Merged PRs (30d)
- 4
Description
Lately we've been seeing lots of timeout failures on lint, and when they do succeed, still taking >1hr:
https://github.com/Rdatatable/data.table/actions/workflows/lint.yaml?query=is%3Afailure
This is due to .Rraw and some inefficiency in {lintr}. We can restore linting these files later, they're not top-level importance anyway.
Contributor guide
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 lint.yaml GitHub Actions workflow and review the linked failed runs to understand how .Rraw files were excluded and where timeouts occur. Restore .Rraw linting only when the workflow completes reliably; done means lint passes without the reported timeout or hour-long runtime.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100