You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix README: clarify Celery is ready but not deployed (subprocess mode active)
Poplar runs jobs as subprocesses (USE_CELERY defaults to false).
Celery tasks exist at full parity but no worker is registered.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -524,8 +524,8 @@ The build context is the **parent directory** containing all sibling repos (not
524
524
- CI/CD pipeline
525
525
- Integration tests against dev workspace
526
526
- Structured logging
527
-
-~~Celery task parity with job scripts~~ (done — tasks connect to existing `redis://bioseed_redis:6379/10` broker, queue `modelseed`, Flower at `poplar:5555`)
528
-
-Dedicated modelseed Celery worker process (currently uses shared worker pool)
527
+
-~~Celery task parity with job scripts~~ (done — `tasks.py` mirrors all job scripts, `celery_app.py` configured for `redis://bioseed_redis:6379/10`)
528
+
-Deploy Celery worker for modelseed queue (tasks are ready but poplar currently runs in subprocess mode; needs `MODELSEED_USE_CELERY=true` + a worker process)
0 commit comments