openedx / openedx/xblocks-core

Investigate/replace GlobalParserTLS thread local

Open
#256 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
0
Forks
15
Avg merge
5d 16m
Merged PRs (30d)
7

Description

Ensure this is async-safe:

https://github.com/openedx/xblocks-core/blob/730174fac55c0e72005a0b58fd83e40244fc8075/xblocks_contrib/problem/xmlparser.py#L68-L75

Because we're in a transitional state, this overlaps with the equivalent code that's still in https://github.com/openedx/openedx-platform/issues/38698

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading xblocks_contrib/problem/xmlparser.py lines 68-75 and the linked openedx-platform issue 38698. Trace how GlobalParserTLS is used and compare the transitional implementations. Done means the parser state is safe across async execution and the overlapping work is accounted for.

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
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.