{"push_id":642336882,"size":1,"distinct_size":1,"ref":"refs/heads/feature/celery","head":"2f6fe45246c74326c6d9d52983b7947e0974a189","before":"bd119d6ebde0576c31d2a61a79568f556fd8336a","commits":[{"sha":"2f6fe45246c74326c6d9d52983b7947e0974a189","author":{"email":"ce870145813bc4437c6d5b2f21d881529250cb53@gmail.com","name":"Flavio Amieiro"},"message":"Fixes and documents the issue with the app import\n\nThe comment above the new import in `pypln/backend/celery_task.py`[1] explains\nthe issue and why this import is necessary. Thank you hidden collateral effects\nfor taking 2 days out of my life.\n\n[1]: \"This import may look like an unused imported, but it is not.\nWhen our base task class is defined, the Celery app must have already been\ninstantiated, otherwise when this code is imported elsewhere (like in a\nclient that will call a task, for example) celery will fallback to the\ndefault app, and our configuration will be ignored. This is not an issue in\nthe documented project layout, because there they import the app in the\nmodule that define the tasks (to use the decorator in `app.task`).\"","distinct":true,"url":"https://api.github.com/repos/flavioamieiro/pypln.backend/commits/2f6fe45246c74326c6d9d52983b7947e0974a189"}]}