magnusmanske / magnusmanske/quickstatements
Batch status "DONE", but many edits still shown as "run"
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 58
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
When running a background batch (created from v1 commands) about a quarter of the edits did not complete. They were left with the status of "run" while the batch showed as "DONE." I tried running those edits again in a new background batch, but the same issue persisted. Ultimately, they did work when running as a temporary batch.
Contributor guide
No contributing guide indexed for this repository
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 comparing background batches 239811 and 239812 with the temporary batch that completed successfully, focusing on how batches created from v1 commands process individual edits. Trace the background-batch handling and identify why edits remain "run" after the batch is marked "DONE." Done means all edits receive their final status and the batch status accurately reflects their completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100