New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Job nodes can't be connected directly to the Start nodes #153
Comments
What database do you use? Does it have 'select .. for update' functionality? Generally task.DoesNotExist could happens b/c celery task started before view code finish and commit. That could happens if lock is not working. |
Sorry, that seems a bug in viewflow. Start nodes do no locking at all, so celery task could start before start view commit the process and task instances |
-pro: 0.10.5 released. Due design flaws in 0.10 the only case for (StartView -> Job) could be fixed. |
btw @boakley you can simplify your view by implementing
|
This doesn't seem to have solved my problem. I upgraded to viewflow-pro 0.10.5, but my tasks still don't do anything. They are still hitting this block of code in job.py:
|
I've got the problem. At the time when flow task is schedulled, the process instance are not commuted. So The only solution for now as i see - is to switch to redis based locks |
I fixed the issue with |
0.10.7.pro released with fix for cache_lock |
In trying to debug why my celery task doesn't seem to do anything I realized that my code was hitting this block in flow_task_decorator:
This causes the body of the celery task to do nothing. There is no output, no log message, no indication whatsoever that there's a problem. The celery log shows that it received, accepted and completed the task, but because the decorator returned nothing, nothing actually executed.
Also, that comment means absolutely nothing to me as a user of viewflow. No rollback has been done to my task (at least, not intentionally), and I have no idea how to fix this problem.
I'm guessing this is related to the fact I'm creating the task from the following custom view:
The text was updated successfully, but these errors were encountered: