How to better understand data mutation/augmentation in runtime
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- developer-experience
Research direction
The issue names no files, tests, or entry points. Start by tracing the runtime pipeline responsible for data mutation and augmentation, then clarify whether the intended outcome is documentation or debugging support; the issue does not define what completion looks like.
Written by the indexing model from the issue text.
Description
Description
Some comments I've gathered from the community survey on the challenges/suggestions section:
Some challenges with local development, debugging ... and the standard learning curve. Since the code being executed is several layers away, it sometimes becomes difficult to debug the pipeline and understand the data mutation/ augmentation happening along the way.
- Dominant language
- Python
- Stars
- 10
- Forks
- 30
- Avg merge
- 5h 49m
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from openedx/openedx-filters
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
openedx/openedx-filters#420 · 2 comments ·
Maintainers usually reply within 1 day
-
Filter Integration Issues After Transition to MFEsMay be free again @mariajgrimaldi claimed this 663 days ago, and no pull request is open. Open
openedx/openedx-filters#255 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
openedx/openedx-filters#245 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
openedx/openedx-filters#196 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 15/100
openedx/openedx-filters#195 ·
Maintainers usually reply within 1 day
All issues in openedx/openedx-filters
Similar issues
-
Layout accepts a step threshold of 0 or less, then in-toto-verify crashes with StopIterationPossibly taken @BahaaMattar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
needs discussion
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openfga/openfga.dev#1436 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
usb-device-hid: MouseInterface reports bInterfaceProtocol 1 (keyboard) instead of 2Possibly taken @Duhan07 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
micropython/micropython-lib#1176 ·