czue / czue/celery-progress

Race between creating ProgressRecorder and setting its progress

Open
#80 6 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
497
Forks
89
PR merge metrics
No merged PRs in 30d

Description

If a ProgressRecorder is created, its state is not initialized until set_progress() is called. During this time, I think there is a race condition where a page calling initProgressBar() can get a bad state === null and fall into onTaskError() during this time.
(progressBarMessageElement will say "Uh-Oh, something went wrong! Unknown state")

Contributor guide

No contributing guide indexed for this repository

Research direction

Trace the ProgressRecorder creation and set_progress() path alongside the initProgressBar() and onTaskError() entry points. Check the interval between creation and progress initialization, then verify that initProgressBar() no longer receives state === null or reports "Unknown state" during that interval.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, python
Domain
full-stack
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.