openedx / openedx/openedx-platform
Investigate/replace use of thread local in ActiveBulkThread
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.2k
- Forks
- 4.4k
- Avg merge
- 6d 18h
- Merged PRs (30d)
- 42
Description
The following is not async-safe:
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 by reading xmodule/modulestore/init.py at lines 168-174 and tracing how ActiveBulkThread uses the thread-local state. Investigate the async-safety concern and identify the required replacement; done means the state no longer relies on the unsafe use while preserving the existing ActiveBulkThread behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100