openedx / openedx/openedx-platform
Create linting to reduce the likelihood that async-unsafe code is merged
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.2k
- Forks
- 4.4k
- Avg merge
- 6d 18h
- Merged PRs (30d)
- 42
Description
Based on @robrap's suggestion, we should set up linting rules to make sure people don't casually re-add global or thread-local code without realizing the async implications.
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
The issue names no files, lint configuration, tests, or specific rules. Start by locating the repository's existing linting setup and documenting how global and thread-local code is currently detected; done means agreed rules are configured and verified to flag async-unsafe additions without blocking safe code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100