Skip to content

Commit e8a21e1

Browse files
jplfariaclaude
andcommitted
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>
1 parent e62ff8d commit e8a21e1

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -524,8 +524,8 @@ The build context is the **parent directory** containing all sibling repos (not
524524
- CI/CD pipeline
525525
- Integration tests against dev workspace
526526
- 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)
529529
- Health check enhancements
530530
- Job store file locking for concurrent access
531531

0 commit comments

Comments
 (0)